Viewing 10 posts - 151 through 160 (of 160 total)
Thanks for the suggestions. I don't know that any of them apply.
SQL Agent is already running (and running other jobs). The Job in question runs every minute from 4 am...
December 13, 2005 at 5:28 pm
Thanks, Linda. I'm loading my demo copy right now, then I'll look it up in BOL.
Elliott
December 1, 2005 at 12:52 pm
Thanks for your reply. We have been scrutinizing the same comparison of features and trying to determine what it means. Nowhere in the Microsoft info do they specifically talk about...
December 1, 2005 at 9:48 am
Thanks for the clarification, Remi. It worked fine.
And thanks for the tip on changing the context, Phil. Now I can script something like:
Set strSQL='USE ' + @db + ' '...
August 26, 2005 at 5:39 pm
Thanks Remi,
sp_MSForeachDB appears to scroll through the databases. But when I attempt to use Information_Schema.columns, the context appears to remain in Master. In other words the column names that are...
August 26, 2005 at 1:41 pm
Run sp_who in Query Analyzer to view the connections to the current database.
See Brian Knight's stored procedure, usp_Kill_Users, to find a useful way to break those connections so you can...
May 25, 2005 at 5:13 pm
The suggestion worked perfectly in SQL 2000. Thanks for your help.
Elliott
May 25, 2005 at 2:32 pm
Yelena, Thanks for your tip. Building the stored procedure right from QA works great and is very efficient.
Elliott
May 19, 2005 at 4:34 pm
Thanks for your help. I was unable to put any commands preceding the "Create Proc" command when writing the proc. UNTIL I used Query Analyzer to edit the proc. Then...
May 19, 2005 at 1:01 pm
Tried that but error message says nothing can be written before the "Create Procedure" statement.
Elliott
May 19, 2005 at 10:25 am
Viewing 10 posts - 151 through 160 (of 160 total)