June 8, 2010 at 4:14 am
If I right click on a database view in SSMS and click on Design SSMS crashes, has anyone else experienced this?
June 11, 2010 at 9:50 am
Any ideas??
June 11, 2010 at 9:55 am
Nope. Any error messages?
June 11, 2010 at 10:49 am
Does this happen with every database, or just views in one particular database? I haven't experienced this error either.
Cindy
June 11, 2010 at 11:00 am
I've just run a few tests and found that it doesn't crash on every view.
On one of the views that it did crash on I get the following message:
"An unhandled win32 exception occurred in SqlWb.exe [508]."
The view itself is a pretty straight forward SELECT statement where the results are pivoted.
My version of SSMS is 9.00.4035.00.
June 11, 2010 at 11:09 am
Same version that I have. Does SSMS crash when you script it as create or alter, or just when it's opened in design? Can you post the code of the view?
Cindy
June 11, 2010 at 11:23 am
If I right click and select Edit it is fine, it only crashes when Design is selected. I cannot post the actual syntax but here is roughly what it looks like:
SELECT
FROM
(
SELECT
FROM
(
SELECT
FROM
WHERE
) fpb
UNPIVOT
(
))unpvt
PIVOT
(
) pvt
There is nothing complicated within the code i.e. any IF statements or dynamic SQL.
June 11, 2010 at 11:58 am
Crashes as in it brings SSMS down or freezes SSMS or what?
Describe what happens step-by-step please.
June 11, 2010 at 12:02 pm
Sounds like the visual designer may not support the pivot/unpivot command and isn't handling it correctly when you attempt to open the view.
June 11, 2010 at 12:05 pm
When I select Design the interfaces freezes for a couple of seconds and then brings up a dialogue box with the error message and a list of debuggers to use for debugging the error. If I choose to not debug the error both the dialogue and SSMS close
June 28, 2010 at 7:59 pm
For me, this was in fact a Visual Designer issue. I stopped trying to design my massive unpivot and just pasted it into a New Query pane (text-only), and it worked flawlessly.
For this who are having it crash inside a business process, try creating it as a query rather than a view. I have no idea if that will help--just a suggestion.
June 29, 2010 at 6:25 am
The Query Builder does have memory / processing limitations compared to the regular query window. We've had a lot of issues with users creating workable queries in the QB that don't work in the QB because of the returning record set, but work in the query windows.
Usually, we get timeouts, though, not full on crashes. Still, I recommend everyone type their code by hand rather than using the drag-n-drop Query Builder. QB causes far too many problems in addition to the timeout issues for it to be a viable solution for DBAs, IMHO.
Don't mistake the limitations of QB with the limitations of views, though. I've used PIVOT and UNPIVOT commands in views a couple of times and don't recall having any issues.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply