Activity overview
Latest activity by jmaumus
Well this is a bit embarrassing, but I think I resolved it.
I am the careful sort, so I have a tendency to Parse the SQL statement before I run it live. This collection of statements would not parse successfully because the Parse was seeing that the Compatibility Level was not set to 100. It was ignoring the fact that I was actually setting it earlier in the script, but that's understandable as it is only Parsing and not running it for real.
When I decided to "buck the tiger's odds" and run the collection of scripts live on a database, it ran just fine. It set the Compat Level to 100, created the procedures, and then set the Compat Level back to 80.
So it will work after all. It just won't Parse.
Thanks for listening, and I am sorry if I wasted your time. [image]
James / comments
Well this is a bit embarrassing, but I think I resolved it.
I am the careful sort, so I have a tendency to Parse the SQL statement before I run it live. This collection of statements would not par...
Hi, James.
Actually, I have a script that I run in sequence before this one to SET QUOTED_IDENTIFIER OFF (because the main script has quotation marks in it that cause SQL to freak if you don't do that. I run a script with that one statement before the main one.
I added the ALTER DATABASE statement to that first script. It runs, but then the main script fails at the CREATE PROCEDURE step because of the AS EXTERNAL part.
I am completely stumped. I can show you the whole script if you want (although I'd rather do that via email). / comments
Hi, James.
Actually, I have a script that I run in sequence before this one to SET QUOTED_IDENTIFIER OFF (because the main script has quotation marks in it that cause SQL to freak if you don't do t...
Running statements that include dynamic database name query
Hi. I am only a "conversational SQL"-ist, so I apologize if I sound like a dope.
I am running MS SQL Server 2008 R2 (MSSMS 10.50.1600.1)
I have a script that I am running on about 20 or so databas...