September 24, 2009 at 6:41 am
Hello, I was in the middle of a production code move last night and I was trying to run in some new stored procedures. When running in the stored procedure, I received this error:
A fatal scripting error occurred.
Incorrect syntax was encountered while parsing GO.
Knowing my syntax "shouldn't" have been incorrect, I started freaking out and commenting lines out trying to get the script to run in. After multiple, unsuccessful attempts, I went to Google.
After going to google, I found this link: http://groups.google.com/group/microsoft.public.sqlserver.tools/browse_thread/thread/1bca620fb84df97e/be5b703af175f85e
This explains that it is Bug ID FDBK44155, and from as much as I've read, Microsoft isn't going to do anything about this. That REALLY frustrates me because I've become accustomed to generating my scripts the exact same way everytime (Script object as Drop To New Query Editor Window, Script object as Create to Clipboard, paste on the drop window). Now I know this will not work.
Does anyone have any workarounds for this, a bug fix, anything!?!?!
September 24, 2009 at 7:11 am
I have to say, I've never come across this bug before and I script things to clipboard and paste them all the time.
It looks like the bug relates to interpretation of Unix style carraige returns, so you could use a text editor with a batch mode to find/replace these I guess?
Or, if this is fixed in SSMS 2008, why not install this on your client machine (it can be installed side by side with 2005).
I've been using the 2008 management studio for quite a while now and it's completely interoperable with 2005 databases and includes some nice enhancements as well (like extra scripting options and a better activity monitor). Sadly no intellisense for 2005 databases though (which I just think is mean spirited ;-))
September 24, 2009 at 8:02 am
It isn't even fixed in 08 either, and another post/article I read said the fix was so tricky (or some word like that) that they weren't even going to include it in SP2.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply