Home Dashboard Directory Help
Search

Data Compression wizard savings calculation crashes SSMS when table has geography column by guitarultimate


Status: 

Closed
 as Duplicate Help for as Duplicate


3
0
Sign in
to vote
Type: Bug
ID: 776803
Opened: 1/17/2013 8:28:43 AM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

When running the data compression wizard and attempting to calculate savings for a table that has a geography type column, management studio stops responding and restarts.

Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
Feb 10 2012 19:39:15
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
Details
Sign in to post a comment.
Posted by Aleksandr Krymskiy on 4/24/2013 at 2:08 PM
SSMS Compression Wizard crashes upon pressing calculate on both SP1 and SP1+CU3 patch levels. My tables do not have geography type columns and SSMS crashes pretty much immediately after clicking "Calculate" with the following:

Problem signature:
Problem Event Name:    CLR20r3
Problem Signature 01:    ssms.exe
Problem Signature 02:    2011.110.3000.0
Problem Signature 03:    5081c1cd
Problem Signature 04:    System.Data
Problem Signature 05:    4.0.30319.18033
Problem Signature 06:    50b5aadf
Problem Signature 07:    2275
Problem Signature 08:    5e
Problem Signature 09:    1MRZFGCRE3EXESRMUATNRQWNNX5CG5HZ
OS Version:    6.2.9200.2.0.0.256.4
Locale ID:    1033
Additional Information 1:    5861
Additional Information 2:    5861822e1919d7c014bbb064c64908b2
Additional Information 3:    f3d5
Additional Information 4:    f3d5be0cad2787556264647dc02181c3
Posted by Microsoft on 1/29/2013 at 4:27 PM
Thank you for reporting this issue - we are investigating and will update you when we have more information.

Thanks,

Alex Grach [MSFT SQL SERVER]
Posted by Sethu Srinivasan on 1/18/2013 at 12:37 PM
Could you please update your SQL 2012 instance to latest Service pack and Cumulative update . You can download from http://technet.microsoft.com/en-us/sqlserver/ff803383.aspx

Let us know if you still see this issue

Thanks
Sethu Srinivasan [MSFT]
SQL Server
Sign in to post a workaround.