%3CLINGO-SUB%20id%3D%22lingo-sub-1706812%22%20slang%3D%22en-US%22%3ERe%3A%20Cumulative%20Update%20%237%20for%20SQL%20Server%202019%20RTM%20(Removed)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1706812%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20timing%20on%20the%20release%20of%20the%20updated%20CU%3F%20We%20have%20to%20schedule%20downtime%20and%20server%20reboots%20for%20this%2C%20and%20would%20like%20to%20know%20an%20approximate%20timeframe%20to%20un-install%20or%20not%20CU7.%26nbsp%3B%3C%2FP%3E%3CP%3EIdeally%20a%20quick%20hotfix%20would%20be%20preferrable.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1707186%22%20slang%3D%22en-US%22%3ERe%3A%20Cumulative%20Update%20%237%20for%20SQL%20Server%202019%20RTM%20(Removed)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1707186%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20what%20you%20want%20to%20see%20the%20same%20day%20after%20finishing%20a%20patch%20cycle!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EETA%20for%20this%20new%20CU%20(or%20a%20hotfix)%20would%20be%20ideal.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1708559%22%20slang%3D%22en-US%22%3ERe%3A%20Cumulative%20Update%20%237%20for%20SQL%20Server%202019%20RTM%20(Removed)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1708559%22%20slang%3D%22en-US%22%3E%3CP%3EI%20know%20bugs%20happen%2C%20but%20this%20is%20not%20instilling%20a%20lot%20of%20confidence%20in%20SQL%202019.%26nbsp%3B%20As%20others%20have%20asked%2C%20ETA%20for%20patch%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1709838%22%20slang%3D%22en-US%22%3ERe%3A%20Cumulative%20Update%20%237%20for%20SQL%20Server%202019%20RTM%20(Removed)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1709838%22%20slang%3D%22en-US%22%3E%3CP%3Eany%20more%20details%20about%20the%26nbsp%3B%3CSPAN%3Edatabase%20snapshots%20issue%3F%20what%20the%20issue%20causes%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1709842%22%20slang%3D%22en-US%22%3ERe%3A%20Cumulative%20Update%20%237%20for%20SQL%20Server%202019%20RTM%20(Removed)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1709842%22%20slang%3D%22en-US%22%3E%3CP%3ECU7%20is%20required%20for%20SCOM%202019%20which%20we%20are%20running.%20An%20update%20on%20the%20date%20of%20the%20upcoming%20release%20would%20be%20great.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1709940%22%20slang%3D%22en-US%22%3ERe%3A%20Cumulative%20Update%20%237%20for%20SQL%20Server%202019%20RTM%20(Removed)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1709940%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F683888%22%20target%3D%22_blank%22%3E%40SrinivasSQL%3C%2FA%3E%26nbsp%3BCould%20you%20please%20share%20more%20detail%20about%20this%20issue%3F%20And%20if%20this%20going%20generate%20the%20memory%20dump%20or%20crash%20sql%20service%3F%3C%2FP%3E%3CP%3EIf%20we%20do%20not%20remove%20cu7%20then%20will%20new%20cu7%20get%20installed%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1710642%22%20slang%3D%22en-US%22%3ERe%3A%20Cumulative%20Update%20%237%20for%20SQL%20Server%202019%20RTM%20(Removed)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1710642%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20other%20issues%20does%20it%20cause%2C%20only%20a%20crash%20when%20trying%20to%20generate%20a%20snapshot%3F%20If%20I%20have%20it%20installed%20but%20don't%20use%20snapshots%20or%20wouldn't%20run%20DBCC%20CHECKDB%20for%20the%20time%20being%20I'm%20going%20to%20be%20safe%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1710664%22%20slang%3D%22en-US%22%3ERe%3A%20Cumulative%20Update%20%237%20for%20SQL%20Server%202019%20RTM%20(Removed)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1710664%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22lia-message-author-with-avatar%22%3E%3CSPAN%20class%3D%22UserName%20lia-user-name%20lia-user-rank-New-Contributor%20lia-component-message-view-widget-author-username%22%3E%3CSPAN%20class%3D%22%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F63643%22%20target%3D%22_blank%22%3E%40Christian%20Araujo%3C%2FA%3E%26nbsp%3Bthere%20is%20no%20mention%20of%20any%20crash%20-%20please%20do%20not%20read%20more%20than%20what%20is%20stated.%20It%20is%20a%20reliability%20issue%20with%20the%20snapshots.%20If%20you%20don't%20use%20any%20of%20the%20affected%20scenarios%2C%20then%20it's%20up%20to%20you%20to%20decide%20whether%20to%20uninstall%20CU7%20or%20not%2C%20while%20waiting%20for%20CU8.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1710818%22%20slang%3D%22en-US%22%3ERe%3A%20Cumulative%20Update%20%237%20for%20SQL%20Server%202019%20RTM%20(Removed)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1710818%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F194232%22%20target%3D%22_blank%22%3E%40Pedro%20Lopes%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1714017%22%20slang%3D%22en-US%22%3ERe%3A%20Cumulative%20Update%20%237%20for%20SQL%20Server%202019%20RTM%20(Removed)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1714017%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310903%22%20target%3D%22_blank%22%3E%40VikasRana2006%3C%2FA%3E%26nbsp%3Bplease%20see%20the%20update.%20There%20is%20no%20crash%20nor%20mem%20dump.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1629317%22%20slang%3D%22en-US%22%3ECumulative%20Update%20%237%20for%20SQL%20Server%202019%20RTM%20(Removed)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1629317%22%20slang%3D%22en-US%22%3E%3CH2%20id%3D%22toc-hId--1271202523%22%20id%3D%22toc-hId--1271202523%22%3EEdit%20(10%2F01%2F2020)%3C%2FH2%3E%0A%3CP%3EWe%20beat%20our%20deadline%20to%20ensure%20those%20that%20had%20not%20removed%20CU7%20could%20have%20a%20reliable%20path%20forward%2C%20so%20SQL%20Server%202019%20CU8%20is%20now%20available.%20See%20the%20announcement%20post%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fsql-server%2Fcumulative-update-8-for-sql-server-2019-rtm%2Fba-p%2F1736647%22%20target%3D%22_self%22%3Ehere%3C%2FA%3E.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1216310310%22%20id%3D%22toc-hId-1216310310%22%3EEdit%20(9%2F24%2F2020)%3C%2FH2%3E%0A%3CDIV%3E%0A%3CDIV%3EThere%20is%20a%20known%20reliability%20issue%20with%20the%20database%20snapshot%20feature%20in%20SQL%20Server%202019%20CU7%2C%20and%20it%20was%20removed%20from%20the%20Download%20Center%2C%20the%20Microsoft%20Update%20Catalog%2C%20and%20Linux%20repositories.%26nbsp%3B%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3EThe%20database%20snapshot%20feature%20is%20used%20explicitly%20with%20the%20CREATE%20DATABASE%20%E2%80%A6%20AS%20SNAPSHOT%20OF%20syntax%2C%20and%20implicitly%20when%20running%20DBCC%20CHECKDB%20(and%20any%20of%20its%20%3C%2FSPAN%3E%3CA%20style%3D%22font-family%3A%20inherit%3B%20background-color%3A%20%23ffffff%3B%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fsql%2Ft-sql%2Fdatabase-console-commands%2Fdbcc-checkdb-transact-sql%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Esubset%20commands%3C%2FA%3E%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3E)%20except%20when%20used%20with%20the%20TABLOCK%20option.%26nbsp%3B%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20face%3D%22inherit%22%3EA%20fix%20will%20be%20included%20in%20the%20upcoming%20SQL%20Server%202019%20Cumulative%20Update%208%20(CU8)%2C%20tentatively%26nbsp%3B%3C%2FFONT%3Escheduled%3CFONT%20face%3D%22inherit%22%3E%26nbsp%3Bfor%20%3CU%3Ethe%20week%20of%20October-12%3C%2FU%3E.%3C%2FFONT%3E%3C%2FP%3E%0A%3C%2FDIV%3E%0A%3CDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3EIf%20you%20had%20downloaded%20the%20CU7%20package%20file%20before%20Sep-23%202020%2C%20it%20is%20advised%20to%20not%20install%20it.%20Instead%2C%20wait%20for%20an%20upcoming%20SQL%20Server%202019%20CU8%20announcement.%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3EIf%20you%20have%20already%20applied%20SQL%20Server%202019%20CU7%2C%20and%20you%20are%20using%20the%20database%20snapshot%20feature%20in%20the%20scenarios%20stated%20above%2C%20please%20uninstall%20it.%20If%20you%20created%20a%20database%20snapshot%20with%20CU7%20installed%2C%20plan%20to%20drop%20the%20snapshot%20before%20or%20after%20uninstalling%20CU7.%20In%20case%20you%20decide%20to%20wait%20for%20CU8%2C%20still%20%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3Eplan%20to%20drop%20the%20snapshots%20created%20with%20CU7.%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3CP%3ETo%20learn%20more%20about%20the%20release%20or%20servicing%20model%2C%20please%20visit%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ECU7%20KB%20Article%3A%20%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fsupport.microsoft.com%252Fen-us%252Fhelp%252F4570012%26amp%3Bdata%3D04%257C01%257Cskandi%2540microsoft.com%257C45bf83bcc1a1499f3e5508d84f690e59%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C637346659920524501%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C1000%26amp%3Bsdata%3DBTVn9aOyrxntmuRBbjTkzyC0nXjl%252BKrDsCQSlRRKBto%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4570012%3C%2FA%3E%3C%2FLI%3E%0A%3CUL%3E%0A%3CLI%3EStarting%20with%20SQL%20Server%202017%2C%20we%20adopted%20a%20new%20modern%20servicing%20model.%20Please%20refer%20to%20our%20blog%20for%20more%20details%20on%20%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fblogs.msdn.microsoft.com%252Fsqlreleaseservices%252Fannouncing-the-modern-servicing-model-for-sql-server%252F%26amp%3Bdata%3D04%257C01%257Cskandi%2540microsoft.com%257C45bf83bcc1a1499f3e5508d84f690e59%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C637346659920524501%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C1000%26amp%3Bsdata%3DHONPS1yvcu4ZXQktbglxPx%252FXXF0uJJZQmYJS9BDD8cw%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EModern%20Servicing%20Model%3C%2FA%3E%20for%20SQL%20Server.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CLI%3EMicrosoft%C2%AE%20SQL%20Server%C2%AE%202019%20RTM%20Latest%20Cumulative%20Update%3A%20%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fwww.microsoft.com%252Fdownload%252Fdetails.aspx%253Fid%253D100809%26amp%3Bdata%3D04%257C01%257Cskandi%2540microsoft.com%257C45bf83bcc1a1499f3e5508d84f690e59%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C637346659920534500%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C1000%26amp%3Bsdata%3D3z6XN17o5vzH3YsCMB47QOLKyKhT6l5SLTzqUBkZDYg%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fdownload%2Fdetails.aspx%3Fid%3D100809%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EUpdate%20Center%20for%20Microsoft%20SQL%20Server%3A%20%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fen-us%252Fsql%252Fdatabase-engine%252Finstall-windows%252Flatest-updates-for-microsoft-sql-server%26amp%3Bdata%3D04%257C01%257Cskandi%2540microsoft.com%257C45bf83bcc1a1499f3e5508d84f690e59%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C637346659920534500%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C1000%26amp%3Bsdata%3Dff5oH%252FuoxyzMzansQ4asKY%252F74YC53uk4QpBaHUozTtg%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsql%2Fdatabase-engine%2Finstall-windows%2Flatest-updates-for-microsoft-sql-server%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1629317%22%20slang%3D%22en-US%22%3E%3CUL%3E%0A%3CLI%3EThere%20is%20a%20known%20issue%20with%20using%20database%20snapshots%20in%20SQL%20Server%202019%20CU7%2C%20and%20it%20was%20removed%20from%20the%20Download%20Center%2C%20the%20Microsoft%20Update%20Catalog%2C%20and%20Linux%20repositories.%20Note%20that%20using%20DBCC%20CHECKDB%20is%20also%20affected%20because%20it%20generates%20a%20database%20snapshot.%20This%20issue%20will%20be%20fixed%20in%20the%20upcoming%20SQL%20Server%202019%20Cumulative%20Update%20(CU).%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1629317%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESQLReleases%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

Edit (10/01/2020)

We beat our deadline to ensure those that had not removed CU7 could have a reliable path forward, so SQL Server 2019 CU8 is now available. See the announcement post here.

Edit (9/24/2020)

There is a known reliability issue with the database snapshot feature in SQL Server 2019 CU7, and it was removed from the Download Center, the Microsoft Update Catalog, and Linux repositories. The database snapshot feature is used explicitly with the CREATE DATABASE … AS SNAPSHOT OF syntax, and implicitly when running DBCC CHECKDB (and any of its subset commands) except when used with the TABLOCK option. 

 

A fix will be included in the upcoming SQL Server 2019 Cumulative Update 8 (CU8), tentatively scheduled for the week of October-12.

 
If you had downloaded the CU7 package file before Sep-23 2020, it is advised to not install it. Instead, wait for an upcoming SQL Server 2019 CU8 announcement.
 
If you have already applied SQL Server 2019 CU7, and you are using the database snapshot feature in the scenarios stated above, please uninstall it. If you created a database snapshot with CU7 installed, plan to drop the snapshot before or after uninstalling CU7. In case you decide to wait for CU8, still plan to drop the snapshots created with CU7.
 

To learn more about the release or servicing model, please visit:

10 Comments
Occasional Visitor

Any timing on the release of the updated CU? We have to schedule downtime and server reboots for this, and would like to know an approximate timeframe to un-install or not CU7. 

Ideally a quick hotfix would be preferrable.

Senior Member

Just what you want to see the same day after finishing a patch cycle!

 

ETA for this new CU (or a hotfix) would be ideal.

Occasional Visitor

I know bugs happen, but this is not instilling a lot of confidence in SQL 2019.  As others have asked, ETA for patch?

Frequent Visitor

any more details about the database snapshots issue? what the issue causes?

Occasional Visitor

CU7 is required for SCOM 2019 which we are running. An update on the date of the upcoming release would be great.

Regular Visitor

@SrinivasSQL Could you please share more detail about this issue? And if this going generate the memory dump or crash sql service?

If we do not remove cu7 then will new cu7 get installed?

New Contributor

What other issues does it cause, only a crash when trying to generate a snapshot? If I have it installed but don't use snapshots or wouldn't run DBCC CHECKDB for the time being I'm going to be safe?

Microsoft
@Christian Araujo there is no mention of any crash - please do not read more than what is stated. It is a reliability issue with the snapshots. If you don't use any of the affected scenarios, then it's up to you to decide whether to uninstall CU7 or not, while waiting for CU8.
New Contributor

Thanks @Pedro Lopes 

Microsoft

@VikasRana2006 please see the update. There is no crash nor mem dump.