Template: CPR – SQL Server 2008 CU individual hotfix

BUG #: 50003750 (SQL Hotfix)BUG #: 98590 (Content Maintenance)BUG #: 50003435 (SQL Hotfix)

Bug #: 103858 (Content Idea)
Bug #: 50003750 (SQL Hotfix)
Bug #: 50003435 (SQL Hotfix)

SQL Server 2005

Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.

SQL Server 2008

Microsoft distribuira ispravke za Microsoft SQL Server 2008 kao jednu datoteku koja se može preuzeti. Pošto su kumulativne ispravke, svako novo izdanje sadrži sve hitne ispravke i sve bezbednosne ispravke koje su bile uključene u prethodne SQL Server 2008 popravi za javnost.

Simptomi

Kada upit obaveštenja kreiraju i uništena u visok koeficijent u Microsoft .NET Framework aplikaciji koja koristi upit obaveštenja, veličinu datoteke evidencije greška Microsoft SQL Server 2008 raste veoma brzo. Pored toga, mnoge evidencije događaja se evidentiraju u evidenciji aplikacije. Do ovog problema dolazi ako je objekat SqlDependency se koristi za upravljanje pretplate na obavijesti u aplikaciji. Poruke koje se evidentiraju se u datoteci evidencije greška SQL Server 2008 izgledati na sledeći način:

Dijalog za upit obaveštenje na razgovor regulator „{E21559B3-B872-DD11-9A07-0015B7D8825A}”. zatvorena zbog sljedeće greške: ' <? xml verzija = „1.0”? >< greška xmlns = „http://schemas.microsoft.com/SQL/ServiceBroker/Error” >< Šifra >-8470 < / kod >< opis > usluga daljinskog opao. < / opis >< / greška >'. Dijalog za upit obaveštenje na razgovor regulator „{589E2621-BA72-DD11-9A07-0015B7D8825A}”. zatvorena zbog sljedeće greške: ' <? xml verzija = „1.0”? >< greška xmlns = „http://schemas.microsoft.com/SQL/ServiceBroker/Error” >< Šifra >-8490 < / kod >< opis > nije moguće pronaći udaljeni servis & apos; SqlQueryNotificationService-e384993c-6978-4af5-8aed-c12181353fe6 & apos; Jer to ne postoji. < / opis >< / greška >'.

Uzrok

Do ovog problema dolazi zato što, kad zoveš SqlDependency.Stop metod, metod nije zapravo otkazivanje pretplate na obavijesti. Kada SQL Server šalje obaveštenje novi upit aplikacije, SQL Server nije moguće pronaći udaljeni servis. Stoga, poruka o grešci se evidentiraju. Ako u visok koeficijent stigne upit obaveštenja, evidenciju raste veoma brzo.

Rešenje

Za SQL Server 2008

Jer se gradi su kumulativne, svako novo izdanje Ispravka sadrži sve hitne ispravke i sve bezbednosne ispravke koje su bile uključene u prethodne SQL Server 2008 popraviti za javnost. Preporučujemo da imate u vidu primenjujete najnovije objavljivanja ispravka koji sadrži ovu zakrpu. Za više informacija, kliknite na sledeći broj članka da biste videli članak u Microsoft bazi znanja:

956909 the SQL Server 2008 gradi objavljene nakon što je pušten je SQL Server 2008

Status

Microsoft je potvrdio da je ovo problem kod Microsoft proizvoda koji su navedeni u odeljku „Odnosi se na”. Ovaj problem je prvi put ispravljen u operativnom sistemu SQL Server 2008 sa servisnim paketom 1.

Više informacija

Za SQL Server 2008

Ovaj prilagodbeni popravak uvodi traga zastava 4133. Možete omogućiti traga zastava 4133 da biste isključili evidenciju grešaka za upit obavijesti. Za više informacija o tome koje datoteke su promenjene i informacija o sve preduslove da primenite kumulativnu ispravku paket koji sadrži prilagodbeni popravak opisan u ovom članku Microsoft baze znanja, kliknite na sledeći broj članka da pogledajte članak u Microsoft bazi znanja:

956909 the SQL Server 2008 koji gradi su za javnost, nakon što je pušten je SQL Server 2008

Reference

Za više informacija o listi gradi koje su dostupne nakon izdavanja programa SQL Server 2008, kliknite na sledeći broj članka da biste videli članak u Microsoft bazi znanja:

956909 the SQL Server 2008 gradi objavljene nakon što je pušten je SQL Server 2008

Za više informacija o modelu za servisiranje Incremental za SQL Server, kliknite na sledeći broj članka da biste videli članak u Microsoft bazi znanja:

935897 an Incremental servisiranje Model dostupan je iz SQL Server tima da dostavi hitnih ispravki za prijavljenih problema Za više informacija o imenovanju šemi ažurirane verzije SQL servera, kliknite na sledeći broj članka da biste videli članak u Microsoft bazi znanja:

822499 nova šema imenovanja za Microsoft SQL Server softver pakete ispravki Za više informacija o terminologiji za ažuriranje softvera, kliknite na sledeći broj članka da biste videli članak u Microsoft bazi znanja:

824684 opis standardne terminologije koja se koristi za opisivanje Microsoftovih softverskih ažuriranja

Author (SME): bruceye
Writer: ericzha; v-sanair
Tech Reviewer: bruceye; joaol
Editor: v-sylvan

Symptoms

When query notifications are created and destroyed in a high ratio in a Microsoft .NET Framework-based application that uses query notifications, the size of the Microsoft SQL Server 2005 error log file grows very quickly. Additionally, many event logs are logged in the Application log. This problem occurs if you use a SqlDependency object to manage the notification subscription in the application.

The messages that are logged in the SQL Server 2005 error log file resemble the following:

The query notification dialog on conversation handle '{E21559B3-B872-DD11-9A07-0015B7D8825A}.' closed due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8470</Code><Description>Remote service has been dropped.</Description></Error>'.

The query notification dialog on conversation handle '{589E2621-BA72-DD11-9A07-0015B7D8825A}.' closed due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8490</Code><Description>Cannot find the remote service 'SqlQueryNotificationService-e384993c-6978-4af5-8aed-c12181353fe6' because it does not exist.</Description></Error>'.

Resolution

For SQL Server 2005

SQL Server 2005 Service Pack 2

Important You must use this fix if you are running SQL Server 2005 Service Pack 2.


The fix for this issue was first released in Cumulative Update 10 for SQL Server 2005 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

956854 Cumulative update package 10 for SQL Server 2005 Service Pack 2

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2005 Service Pack 3

Important You must use this fix if you are running SQL Server 2005 Service Pack 3.


The fix for this issue was also later released in Cumulative Update 1 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

959195 Cumulative update package 1 for SQL Server 2005 Service Pack 3

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released

Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

More Information

For SQL Server 2005

This hotfix introduces trace flag 4133. You can enable trace flag 4133 to turn off the error log for query notifications.

For more information about how to enable a trace flag in SQL Server 2005, see the "Remarks" section of the following Microsoft Developer Network (MSDN) Web site:

http://msdn2.microsoft.com/en-us/library/ms188396.aspx

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

956854 Cumulative update package 10 for SQL Server 2005 Service Pack 2

References

For more information about the list of builds that are available after the release of SQL Server 2005, click the following article number to view the article in the Microsoft Knowledge Base:
 

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
 

For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
 

913089 How to obtain the latest service pack for SQL Server 2005
 

For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:

http://go.microsoft.com/fwlink/?LinkId=71711

Potrebna vam je dodatna pomoć?

Unapredite veštine
Istražite obuku
Prvi nabavite nove funkcije
Pridružite se Microsoft insajdere

Da li su vam ove informacije koristile?

Koliko ste zadovoljni kvalitetom prevoda?
Šta je uticalo na vaše iskustvo?

Hvala vam na povratnim informacijama!

×