Activity overview
Latest activity by ryanmccauley
I can't provide a backup, since it's our financial database, but I've replicated the problem with an empty database, so you should be able to reproduce it. I've uploaded the files you'll need to http://www.trycatchfinally.net/Download ... Crash1.zip, and to cause this behavior, you'll need a linked server.
Here are the steps to follow:
1. Create a linked server
2. On the linked server, in any database, run "Create Tables.sql" to create these two tables (fixing db name as necessary).
3. On your main SQL Server, in any database, run "Create Views.sql" to create two views that pull data from that linked server (fixing linked server and db names as necessary).
4. On your main server, when in the master database, load "Script.sql" (fixing linked server and db names as necessary). SSMS will behave normally.
5. Switch your active database to the one containing the two views. SSMS will stop responding and RAM allocation will climb without stopping.
Let me know if you have any questions, or if this does not replicate the issue for you. In production, the local server is SQL2005 and the linked server is SQL2000, but I've replicated with SQL2005 for both. / comments
I can't provide a backup, since it's our financial database, but I've replicated the problem with an empty database, so you should be able to reproduce it. I've uploaded the files you'll need to ht...
OutOfMemoryException when analyzing new script
As soon as I load a particular script, SSMS locks up for about 5 minutes, and then I get an Out of memory exception. I've included the exception text below. Though I can't send a copy of the databa...