How to delete SQL Server Database Mail history WITHOUT stored proceduresWhy use both TRUNCATE and DROP?Database security through stored proceduresHow to split tables without affecting all stored proceduresHow To Profile Stored ProceduresHow to keep history of SQL Server stored procedure revisions~2 Hours after a large insert SQL Server gets “I/O requests taking longer than 15 seconds to complete”High write latancy in temp dbSQL Server's “Total Server Memory” consumption stagnant for months with 64GB+ more availableSQL Server and TFS - How to rename stored proceduresTransaction log filling the drive if mirroring failsWhat Triggers sp_recompile in database without triggers, stored procedures, etc?

Realistic, logical way for men with medieval-era weaponry to compete with much larger and physically stronger foes

Jam with honey & without pectin has a saucy consistency always

Parallelized for loop in Bash

Should I worry about having my credit pulled multiple times while car shopping?

Fastest way from 10 to 1 with everyone in between

Why are backslashes included in this shell script?

Commencez à vous connecter -- I don't understand the phrasing of this

My parents claim they cannot pay for my college education; what are my options?

Idiom for 'person who gets violent when drunk"

How can religions without a hell discourage evil-doing?

Why did the AvroCar fail to fly above 3 feet?

Why does there seem to be an extreme lack of public trashcans in Taiwan?

Does an African-American baby born in Youngstown, Ohio have a higher infant mortality rate than a baby born in Iran?

Why is gun control associated with the socially liberal Democratic party?

Harley Davidson clattering noise from engine, backfire and failure to start

Am I allowed to determine tenets of my contract as a warlock?

How to represent jealousy in a cute way?

Can artificial satellite positions affect tides?

Shouldn't it take more energy to break CO2 compared to CO?

What game uses dice with compass point arrows, forbidden signs, explosions, arrows and targeting reticles?

Past vs. present tense when referring to a fictional character

What's the reason for the decade jump in the recent X-Men trilogy?

Approach sick days in feedback meeting

typeid("") != typeid(const char*)



How to delete SQL Server Database Mail history WITHOUT stored procedures


Why use both TRUNCATE and DROP?Database security through stored proceduresHow to split tables without affecting all stored proceduresHow To Profile Stored ProceduresHow to keep history of SQL Server stored procedure revisions~2 Hours after a large insert SQL Server gets “I/O requests taking longer than 15 seconds to complete”High write latancy in temp dbSQL Server's “Total Server Memory” consumption stagnant for months with 64GB+ more availableSQL Server and TFS - How to rename stored proceduresTransaction log filling the drive if mirroring failsWhat Triggers sp_recompile in database without triggers, stored procedures, etc?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








1















This is really straight forward. The documented way to delete Database mail history in SQL server is to use the following two stored procedures:sysmail_delete_mailitems_sp and sysmail_delete_log_sp



Great. But what happens when apparently billions of emails are stored in here taking up several hundred gigabytes in msdb, and even the process of trying to clear only 100 days worth of email takes hours or days?



I don't want any history and I don't want to wait until I'm a senior citizen to clear the list of e-mail history. How do I truncate this history in one quick transaction?



So far my efforts at using the built in procedures have been futile - growing tempdb and msdb to terabytes in size and sitting "executing" for hours on end. Any attempt to cancel it results in the entire transaction being rolled back. It so far hasn't even been possible to count the number of emails that exist in the history - it's that bad.










share|improve this question













migrated from serverfault.com May 30 at 0:44


This question came from our site for system and network administrators.
























    1















    This is really straight forward. The documented way to delete Database mail history in SQL server is to use the following two stored procedures:sysmail_delete_mailitems_sp and sysmail_delete_log_sp



    Great. But what happens when apparently billions of emails are stored in here taking up several hundred gigabytes in msdb, and even the process of trying to clear only 100 days worth of email takes hours or days?



    I don't want any history and I don't want to wait until I'm a senior citizen to clear the list of e-mail history. How do I truncate this history in one quick transaction?



    So far my efforts at using the built in procedures have been futile - growing tempdb and msdb to terabytes in size and sitting "executing" for hours on end. Any attempt to cancel it results in the entire transaction being rolled back. It so far hasn't even been possible to count the number of emails that exist in the history - it's that bad.










    share|improve this question













    migrated from serverfault.com May 30 at 0:44


    This question came from our site for system and network administrators.




















      1












      1








      1








      This is really straight forward. The documented way to delete Database mail history in SQL server is to use the following two stored procedures:sysmail_delete_mailitems_sp and sysmail_delete_log_sp



      Great. But what happens when apparently billions of emails are stored in here taking up several hundred gigabytes in msdb, and even the process of trying to clear only 100 days worth of email takes hours or days?



      I don't want any history and I don't want to wait until I'm a senior citizen to clear the list of e-mail history. How do I truncate this history in one quick transaction?



      So far my efforts at using the built in procedures have been futile - growing tempdb and msdb to terabytes in size and sitting "executing" for hours on end. Any attempt to cancel it results in the entire transaction being rolled back. It so far hasn't even been possible to count the number of emails that exist in the history - it's that bad.










      share|improve this question














      This is really straight forward. The documented way to delete Database mail history in SQL server is to use the following two stored procedures:sysmail_delete_mailitems_sp and sysmail_delete_log_sp



      Great. But what happens when apparently billions of emails are stored in here taking up several hundred gigabytes in msdb, and even the process of trying to clear only 100 days worth of email takes hours or days?



      I don't want any history and I don't want to wait until I'm a senior citizen to clear the list of e-mail history. How do I truncate this history in one quick transaction?



      So far my efforts at using the built in procedures have been futile - growing tempdb and msdb to terabytes in size and sitting "executing" for hours on end. Any attempt to cancel it results in the entire transaction being rolled back. It so far hasn't even been possible to count the number of emails that exist in the history - it's that bad.







      sql-server






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked May 29 at 21:06









      AppleoddityAppleoddity

      1163




      1163




      migrated from serverfault.com May 30 at 0:44


      This question came from our site for system and network administrators.









      migrated from serverfault.com May 30 at 0:44


      This question came from our site for system and network administrators.






















          2 Answers
          2






          active

          oldest

          votes


















          2














          One idea could be:



          1. script out CREATE TABLE for sysmail_attachments, sysmail_send_retries, sysmail_mailitems, and sysmail_log

          2. start a transaction

          3. drop the tables in that order

          4. create the tables again using the script from 1.

          5. commit the transaction

          6. create a job that purges those tables regularly (like, once an hour, from the sounds of it), also in that order





          share|improve this answer























          • Thank you for your answer. I had already decided to try a similar method of dropping the foreign key constraints and truncating the tables. It seems to have worked properly. Take a look and see if you see any issues in my answer. I appreciate your help!

            – Appleoddity
            May 30 at 5:37











          • @Appleoddity well, removing keys and truncating is a lot more work, obviously, and there is a tiny bit more logging involved, and some more too with the FK changes, but whatever floats your boat I guess.

            – Aaron Bertrand
            May 30 at 10:39



















          1














          Building on @Aaron Bertrand's answer. I decided to delete the foreign key constraints and truncate the tables and then recreate the constraints.



          This is the script I used to clear the e-mail history and it took about 1 second to run total:



          BEGIN TRANSACTION;

          USE MSDB;

          ALTER TABLE [dbo].[sysmail_attachments] DROP [FK_sysmail_mailitems_mailitem_id];
          TRUNCATE TABLE [dbo].[sysmail_attachments];

          ALTER TABLE [dbo].[sysmail_send_retries] DROP [FK_mailitems_mailitem_id];
          TRUNCATE TABLE [dbo].[sysmail_send_retries];

          TRUNCATE TABLE [dbo].[sysmail_mailitems];

          TRUNCATE TABLE [dbo].[sysmail_log];

          ALTER TABLE [dbo].[sysmail_attachments] WITH CHECK ADD CONSTRAINT [FK_sysmail_mailitems_mailitem_id] FOREIGN KEY([mailitem_id])
          REFERENCES [dbo].[sysmail_mailitems] ([mailitem_id])
          ON DELETE CASCADE
          ALTER TABLE [dbo].[sysmail_attachments] CHECK CONSTRAINT [FK_sysmail_mailitems_mailitem_id]

          ALTER TABLE [dbo].[sysmail_send_retries] WITH CHECK ADD CONSTRAINT [FK_mailitems_mailitem_id] FOREIGN KEY([mailitem_id])
          REFERENCES [dbo].[sysmail_mailitems] ([mailitem_id])
          ON DELETE CASCADE
          ALTER TABLE [dbo].[sysmail_send_retries] CHECK CONSTRAINT [FK_mailitems_mailitem_id]

          COMMIT;


          After that, it was just a matter or shrinking (and setting the initial size of) the msdb and tempdb databases.






          share|improve this answer























            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "182"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f239409%2fhow-to-delete-sql-server-database-mail-history-without-stored-procedures%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            2














            One idea could be:



            1. script out CREATE TABLE for sysmail_attachments, sysmail_send_retries, sysmail_mailitems, and sysmail_log

            2. start a transaction

            3. drop the tables in that order

            4. create the tables again using the script from 1.

            5. commit the transaction

            6. create a job that purges those tables regularly (like, once an hour, from the sounds of it), also in that order





            share|improve this answer























            • Thank you for your answer. I had already decided to try a similar method of dropping the foreign key constraints and truncating the tables. It seems to have worked properly. Take a look and see if you see any issues in my answer. I appreciate your help!

              – Appleoddity
              May 30 at 5:37











            • @Appleoddity well, removing keys and truncating is a lot more work, obviously, and there is a tiny bit more logging involved, and some more too with the FK changes, but whatever floats your boat I guess.

              – Aaron Bertrand
              May 30 at 10:39
















            2














            One idea could be:



            1. script out CREATE TABLE for sysmail_attachments, sysmail_send_retries, sysmail_mailitems, and sysmail_log

            2. start a transaction

            3. drop the tables in that order

            4. create the tables again using the script from 1.

            5. commit the transaction

            6. create a job that purges those tables regularly (like, once an hour, from the sounds of it), also in that order





            share|improve this answer























            • Thank you for your answer. I had already decided to try a similar method of dropping the foreign key constraints and truncating the tables. It seems to have worked properly. Take a look and see if you see any issues in my answer. I appreciate your help!

              – Appleoddity
              May 30 at 5:37











            • @Appleoddity well, removing keys and truncating is a lot more work, obviously, and there is a tiny bit more logging involved, and some more too with the FK changes, but whatever floats your boat I guess.

              – Aaron Bertrand
              May 30 at 10:39














            2












            2








            2







            One idea could be:



            1. script out CREATE TABLE for sysmail_attachments, sysmail_send_retries, sysmail_mailitems, and sysmail_log

            2. start a transaction

            3. drop the tables in that order

            4. create the tables again using the script from 1.

            5. commit the transaction

            6. create a job that purges those tables regularly (like, once an hour, from the sounds of it), also in that order





            share|improve this answer













            One idea could be:



            1. script out CREATE TABLE for sysmail_attachments, sysmail_send_retries, sysmail_mailitems, and sysmail_log

            2. start a transaction

            3. drop the tables in that order

            4. create the tables again using the script from 1.

            5. commit the transaction

            6. create a job that purges those tables regularly (like, once an hour, from the sounds of it), also in that order






            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered May 30 at 1:19









            Aaron BertrandAaron Bertrand

            157k18307514




            157k18307514












            • Thank you for your answer. I had already decided to try a similar method of dropping the foreign key constraints and truncating the tables. It seems to have worked properly. Take a look and see if you see any issues in my answer. I appreciate your help!

              – Appleoddity
              May 30 at 5:37











            • @Appleoddity well, removing keys and truncating is a lot more work, obviously, and there is a tiny bit more logging involved, and some more too with the FK changes, but whatever floats your boat I guess.

              – Aaron Bertrand
              May 30 at 10:39


















            • Thank you for your answer. I had already decided to try a similar method of dropping the foreign key constraints and truncating the tables. It seems to have worked properly. Take a look and see if you see any issues in my answer. I appreciate your help!

              – Appleoddity
              May 30 at 5:37











            • @Appleoddity well, removing keys and truncating is a lot more work, obviously, and there is a tiny bit more logging involved, and some more too with the FK changes, but whatever floats your boat I guess.

              – Aaron Bertrand
              May 30 at 10:39

















            Thank you for your answer. I had already decided to try a similar method of dropping the foreign key constraints and truncating the tables. It seems to have worked properly. Take a look and see if you see any issues in my answer. I appreciate your help!

            – Appleoddity
            May 30 at 5:37





            Thank you for your answer. I had already decided to try a similar method of dropping the foreign key constraints and truncating the tables. It seems to have worked properly. Take a look and see if you see any issues in my answer. I appreciate your help!

            – Appleoddity
            May 30 at 5:37













            @Appleoddity well, removing keys and truncating is a lot more work, obviously, and there is a tiny bit more logging involved, and some more too with the FK changes, but whatever floats your boat I guess.

            – Aaron Bertrand
            May 30 at 10:39






            @Appleoddity well, removing keys and truncating is a lot more work, obviously, and there is a tiny bit more logging involved, and some more too with the FK changes, but whatever floats your boat I guess.

            – Aaron Bertrand
            May 30 at 10:39














            1














            Building on @Aaron Bertrand's answer. I decided to delete the foreign key constraints and truncate the tables and then recreate the constraints.



            This is the script I used to clear the e-mail history and it took about 1 second to run total:



            BEGIN TRANSACTION;

            USE MSDB;

            ALTER TABLE [dbo].[sysmail_attachments] DROP [FK_sysmail_mailitems_mailitem_id];
            TRUNCATE TABLE [dbo].[sysmail_attachments];

            ALTER TABLE [dbo].[sysmail_send_retries] DROP [FK_mailitems_mailitem_id];
            TRUNCATE TABLE [dbo].[sysmail_send_retries];

            TRUNCATE TABLE [dbo].[sysmail_mailitems];

            TRUNCATE TABLE [dbo].[sysmail_log];

            ALTER TABLE [dbo].[sysmail_attachments] WITH CHECK ADD CONSTRAINT [FK_sysmail_mailitems_mailitem_id] FOREIGN KEY([mailitem_id])
            REFERENCES [dbo].[sysmail_mailitems] ([mailitem_id])
            ON DELETE CASCADE
            ALTER TABLE [dbo].[sysmail_attachments] CHECK CONSTRAINT [FK_sysmail_mailitems_mailitem_id]

            ALTER TABLE [dbo].[sysmail_send_retries] WITH CHECK ADD CONSTRAINT [FK_mailitems_mailitem_id] FOREIGN KEY([mailitem_id])
            REFERENCES [dbo].[sysmail_mailitems] ([mailitem_id])
            ON DELETE CASCADE
            ALTER TABLE [dbo].[sysmail_send_retries] CHECK CONSTRAINT [FK_mailitems_mailitem_id]

            COMMIT;


            After that, it was just a matter or shrinking (and setting the initial size of) the msdb and tempdb databases.






            share|improve this answer



























              1














              Building on @Aaron Bertrand's answer. I decided to delete the foreign key constraints and truncate the tables and then recreate the constraints.



              This is the script I used to clear the e-mail history and it took about 1 second to run total:



              BEGIN TRANSACTION;

              USE MSDB;

              ALTER TABLE [dbo].[sysmail_attachments] DROP [FK_sysmail_mailitems_mailitem_id];
              TRUNCATE TABLE [dbo].[sysmail_attachments];

              ALTER TABLE [dbo].[sysmail_send_retries] DROP [FK_mailitems_mailitem_id];
              TRUNCATE TABLE [dbo].[sysmail_send_retries];

              TRUNCATE TABLE [dbo].[sysmail_mailitems];

              TRUNCATE TABLE [dbo].[sysmail_log];

              ALTER TABLE [dbo].[sysmail_attachments] WITH CHECK ADD CONSTRAINT [FK_sysmail_mailitems_mailitem_id] FOREIGN KEY([mailitem_id])
              REFERENCES [dbo].[sysmail_mailitems] ([mailitem_id])
              ON DELETE CASCADE
              ALTER TABLE [dbo].[sysmail_attachments] CHECK CONSTRAINT [FK_sysmail_mailitems_mailitem_id]

              ALTER TABLE [dbo].[sysmail_send_retries] WITH CHECK ADD CONSTRAINT [FK_mailitems_mailitem_id] FOREIGN KEY([mailitem_id])
              REFERENCES [dbo].[sysmail_mailitems] ([mailitem_id])
              ON DELETE CASCADE
              ALTER TABLE [dbo].[sysmail_send_retries] CHECK CONSTRAINT [FK_mailitems_mailitem_id]

              COMMIT;


              After that, it was just a matter or shrinking (and setting the initial size of) the msdb and tempdb databases.






              share|improve this answer

























                1












                1








                1







                Building on @Aaron Bertrand's answer. I decided to delete the foreign key constraints and truncate the tables and then recreate the constraints.



                This is the script I used to clear the e-mail history and it took about 1 second to run total:



                BEGIN TRANSACTION;

                USE MSDB;

                ALTER TABLE [dbo].[sysmail_attachments] DROP [FK_sysmail_mailitems_mailitem_id];
                TRUNCATE TABLE [dbo].[sysmail_attachments];

                ALTER TABLE [dbo].[sysmail_send_retries] DROP [FK_mailitems_mailitem_id];
                TRUNCATE TABLE [dbo].[sysmail_send_retries];

                TRUNCATE TABLE [dbo].[sysmail_mailitems];

                TRUNCATE TABLE [dbo].[sysmail_log];

                ALTER TABLE [dbo].[sysmail_attachments] WITH CHECK ADD CONSTRAINT [FK_sysmail_mailitems_mailitem_id] FOREIGN KEY([mailitem_id])
                REFERENCES [dbo].[sysmail_mailitems] ([mailitem_id])
                ON DELETE CASCADE
                ALTER TABLE [dbo].[sysmail_attachments] CHECK CONSTRAINT [FK_sysmail_mailitems_mailitem_id]

                ALTER TABLE [dbo].[sysmail_send_retries] WITH CHECK ADD CONSTRAINT [FK_mailitems_mailitem_id] FOREIGN KEY([mailitem_id])
                REFERENCES [dbo].[sysmail_mailitems] ([mailitem_id])
                ON DELETE CASCADE
                ALTER TABLE [dbo].[sysmail_send_retries] CHECK CONSTRAINT [FK_mailitems_mailitem_id]

                COMMIT;


                After that, it was just a matter or shrinking (and setting the initial size of) the msdb and tempdb databases.






                share|improve this answer













                Building on @Aaron Bertrand's answer. I decided to delete the foreign key constraints and truncate the tables and then recreate the constraints.



                This is the script I used to clear the e-mail history and it took about 1 second to run total:



                BEGIN TRANSACTION;

                USE MSDB;

                ALTER TABLE [dbo].[sysmail_attachments] DROP [FK_sysmail_mailitems_mailitem_id];
                TRUNCATE TABLE [dbo].[sysmail_attachments];

                ALTER TABLE [dbo].[sysmail_send_retries] DROP [FK_mailitems_mailitem_id];
                TRUNCATE TABLE [dbo].[sysmail_send_retries];

                TRUNCATE TABLE [dbo].[sysmail_mailitems];

                TRUNCATE TABLE [dbo].[sysmail_log];

                ALTER TABLE [dbo].[sysmail_attachments] WITH CHECK ADD CONSTRAINT [FK_sysmail_mailitems_mailitem_id] FOREIGN KEY([mailitem_id])
                REFERENCES [dbo].[sysmail_mailitems] ([mailitem_id])
                ON DELETE CASCADE
                ALTER TABLE [dbo].[sysmail_attachments] CHECK CONSTRAINT [FK_sysmail_mailitems_mailitem_id]

                ALTER TABLE [dbo].[sysmail_send_retries] WITH CHECK ADD CONSTRAINT [FK_mailitems_mailitem_id] FOREIGN KEY([mailitem_id])
                REFERENCES [dbo].[sysmail_mailitems] ([mailitem_id])
                ON DELETE CASCADE
                ALTER TABLE [dbo].[sysmail_send_retries] CHECK CONSTRAINT [FK_mailitems_mailitem_id]

                COMMIT;


                After that, it was just a matter or shrinking (and setting the initial size of) the msdb and tempdb databases.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered May 30 at 5:34









                AppleoddityAppleoddity

                1163




                1163



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Database Administrators Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f239409%2fhow-to-delete-sql-server-database-mail-history-without-stored-procedures%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Club Baloncesto Breogán Índice Historia | Pavillón | Nome | O Breogán na cultura popular | Xogadores | Adestradores | Presidentes | Palmarés | Historial | Líderes | Notas | Véxase tamén | Menú de navegacióncbbreogan.galCadroGuía oficial da ACB 2009-10, páxina 201Guía oficial ACB 1992, páxina 183. Editorial DB.É de 6.500 espectadores sentados axeitándose á última normativa"Estudiantes Junior, entre as mellores canteiras"o orixinalHemeroteca El Mundo Deportivo, 16 setembro de 1970, páxina 12Historia do BreogánAlfredo Pérez, o último canoneiroHistoria C.B. BreogánHemeroteca de El Mundo DeportivoJimmy Wright, norteamericano do Breogán deixará Lugo por ameazas de morteResultados de Breogán en 1986-87Resultados de Breogán en 1990-91Ficha de Velimir Perasović en acb.comResultados de Breogán en 1994-95Breogán arrasa al Barça. "El Mundo Deportivo", 27 de setembro de 1999, páxina 58CB Breogán - FC BarcelonaA FEB invita a participar nunha nova Liga EuropeaCharlie Bell na prensa estatalMáximos anotadores 2005Tempada 2005-06 : Tódolos Xogadores da Xornada""Non quero pensar nunha man negra, mais pregúntome que está a pasar""o orixinalRaúl López, orgulloso dos xogadores, presume da boa saúde económica do BreogánJulio González confirma que cesa como presidente del BreogánHomenaxe a Lisardo GómezA tempada do rexurdimento celesteEntrevista a Lisardo GómezEl COB dinamita el Pazo para forzar el quinto (69-73)Cafés Candelas, patrocinador del CB Breogán"Suso Lázare, novo presidente do Breogán"o orixinalCafés Candelas Breogán firma el mayor triunfo de la historiaEl Breogán realizará 17 homenajes por su cincuenta aniversario"O Breogán honra ao seu fundador e primeiro presidente"o orixinalMiguel Giao recibiu a homenaxe do PazoHomenaxe aos primeiros gladiadores celestesO home que nos amosa como ver o Breo co corazónTita Franco será homenaxeada polos #50anosdeBreoJulio Vila recibirá unha homenaxe in memoriam polos #50anosdeBreo"O Breogán homenaxeará aos seus aboados máis veteráns"Pechada ovación a «Capi» Sanmartín e Ricardo «Corazón de González»Homenaxe por décadas de informaciónPaco García volve ao Pazo con motivo do 50 aniversario"Resultados y clasificaciones""O Cafés Candelas Breogán, campión da Copa Princesa""O Cafés Candelas Breogán, equipo ACB"C.B. Breogán"Proxecto social"o orixinal"Centros asociados"o orixinalFicha en imdb.comMario Camus trata la recuperación del amor en 'La vieja música', su última película"Páxina web oficial""Club Baloncesto Breogán""C. B. Breogán S.A.D."eehttp://www.fegaba.com

                    Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

                    Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020