November 24, 2008 at 4:09 pm
Comments posted to this topic are about the item Another way to track the database data growth
December 22, 2008 at 8:06 am
It wasn't difficult to find the ???? in the script and was able to get it to run. However due to the nature of the way some of my databases are named I had to make a small revision to get the script to run completely. The line of code in both procedures is as follows:
'Use '+@dbName+'; '+
I changed it to:
'Use ['+@dbName+']; '+
and this was able to correct the problem. Thanks for the script. I have a project that was handed me to provision the production SQL Server box for 2009.
Kurt
Kurt W. Zimmerman
SR DBA
Lefrak Organization
New York, NY
http://www.linkedin.com/in/kurtwzimmerman
March 12, 2011 at 11:38 am
Hey Max,
While reading your article i checked the script in sql server 2005,
it was giving me the error.
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(7 row(s) affected)
Msg 111, Level 15, State 1, Procedure #uspGetFileStats, Line 9
'CREATE/ALTER PROCEDURE' must be the first statement in a query batch.
Msg 213, Level 16, State 7, Line 1
Insert Error: Column name or number of supplied values does not match table definition.
do you have any change in the script?
Saurabh
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply