Comments
Sort by recent activity
Cool. I have repeated what you have described and can confirm that this happens to me as well. I am running SQL2005 SP2.
[Edit]
Actually, I did not crash (at least not yet) and clicking on the close x for the query did eventually bring up the save dialog and I could just click No and all was then well. That is about all I could do though.
Dave / comments
Cool. I have repeated what you have described and can confirm that this happens to me as well. I am running SQL2005 SP2.
[Edit]
Actually, I did not crash (at least not yet) and clicking on the cl...
I can also confirm that SQL Prompt 3 works very well with Office 2007 installed. I experienced no issues at all. I was also running on Vista Ultimate and found no problems there. In fact, Version 3 is required IMHO for Vista as version 2 runs very slow and does some weird things.
You can actually watch it back up and type out the snippets as if you were typing it yourself. Neat to watch but completely unusable. / comments
I can also confirm that SQL Prompt 3 works very well with Office 2007 installed. I experienced no issues at all. I was also running on Vista Ultimate and found no problems there. In fact, Versi...
The word "refactor" comes to mind. A 3500 line script is madness.
My $0.02 / comments
The word "refactor" comes to mind. A 3500 line script is madness.
My $0.02
The only time I experienced horrible performance due to SQL Prompt was after installing a service pack. (for Visual Studio OR SQL Server) I found that uninstalling and reinstalling SQL Prompt fixed everything up. This has happened to me a couple of times. / comments
The only time I experienced horrible performance due to SQL Prompt was after installing a service pack. (for Visual Studio OR SQL Server) I found that uninstalling and reinstalling SQL Prompt fixe...
Hi Tilman,
See screen shot here: http://www.totzke.ca/sqlprompt.jpg
I cleared the cache and closed all current connections. The problem still exists. All columns that are nvarchar(50) were created as such originally and display in SQL Prompt as nvarchar(100). You will see a column now that is nvarchar(300) and SQL Prompt shows it as nvarchar(600).
It is likely that SQL Prompt is relying on the column length which for nvarchar columns shows up as double because of their support for DBCS.
Dave / comments
Hi Tilman,
See screen shot here:http://www.totzke.ca/sqlprompt.jpg
I cleared the cache and closed all current connections. The problem still exists. All columns that are nvarchar(50) were created...