Viewing 15 posts - 211 through 225 (of 285 total)
AlexSQLForums (11/18/2009)
http://www.sqlservercentral.com/Forums/Topic326235-5-1.aspx
Sorry, I'm looking for a "65536" hit on the status column, rather than the status2 column.
November 18, 2009 at 7:01 pm
Or this to see when the most recent FULL, DIFF or LOG backup was for each database.
.
.
.
Here's some code I had for finding failed jobs:
.
.
.
Thanks, this helps a lot!
November 17, 2009 at 7:19 am
homebrew01 (11/16/2009)
If the job is failing, you should configure it to send you an email notification.
In a perfect world, I would agree with you on this point. However, our site...
November 16, 2009 at 6:22 pm
Thanks for the recommendation. I ran across "Microsoft SQL Server 2005 Unleashed" too:
http://www.amazon.com/Microsoft-SQL-Server-2005-Unleashed/dp/0672328240/ref=pd_bxgy_b_img_c
It looks useful as well.
September 24, 2009 at 7:44 am
I had similar needs a while back, and I couldn't find a way to retrieve the information without first pushing the output into a temporary table with code something like:
...
February 28, 2005 at 1:08 pm
Good point. I had forgotten about the -h-1 parameter for osql.exe.
February 2, 2005 at 12:34 pm
I found this link (http://www.sqlmonster.com/Uwe/Forum.aspx/ms-sql-server/1763/ISQL-and-OSQL-Output-Lines-Wrapped-Around-at-256-Characters) that says that print always wraps at 256 characters, regardless of the -w parameter setting for osql.exe. This appears to be true. What a dumb default... ...
February 1, 2005 at 2:00 pm
July 22, 2004 at 5:54 am
I normally don’t cross post, but I didn’t want my question to get lost in the middle of this thread, and the people who have...
July 21, 2004 at 9:39 am
FYI -
We use DNS CNAMEs in order to avoid hardcoding server names.
July 6, 2004 at 12:09 pm
No, each server has a script of its own. Essentially, each script consists of a series of SQLMAINT.EXE commands. For each server, each job runs in a serial fashion in...
June 15, 2004 at 11:39 am
Joe,
The odd thing is that this code has not changed in over a year, and it used to work fine. The overall sizes of the databases are not that much...
June 15, 2004 at 9:39 am
By the way, database size does not seem to make a difference. We are getting the same error on the pubs and Northwind databases too.
Jon
June 14, 2004 at 5:00 am
My 2 cts...
WARNING: We created a trigger a while back that hits an executable. It has been my experience that such a configuration can generate some really wild debugging...
June 10, 2004 at 9:47 am
My 2 cts...
I tend to leave the logins defaulted to the master database because I have had SQL Server upgrades to choke when it found users defaulted anywhere else.
Jon
June 4, 2004 at 11:13 am
Viewing 15 posts - 211 through 225 (of 285 total)