Viewing 10 posts - 16 through 25 (of 25 total)
I'm having this problem occasionaly in my log shipping jobs. The problem for me turns out to be corrupted log or full backups. After loading the bad backup the db...
October 23, 2006 at 12:29 pm
While I'm sure there are plenty of third party tolls that do this, I actually found a great set of scripts designed by someone on this site and posted for...
July 27, 2006 at 2:00 pm
I'm with Chris Smith, leave this guy alone! Without the rest of the story you don't know what the purpose of the design is. I've seen date lookup tables used...
June 15, 2006 at 8:38 am
What a terrible idea!
Is the person who told you to do that in line for the same promotion as you? Sounds like a setup.
I'd sooner give my boss...
March 9, 2005 at 7:36 am
I have the same problem, need to be able to continue executing within a stored proc after an error occurs in a linked server query or call to a remote...
March 2, 2005 at 4:18 pm
Believe it or not it's easy as can be. Just reference the value of User.USerID. That contains the NT login of the user running the report, simple and easy...for once!
January 25, 2005 at 8:18 am
This is a good article to read if you'r walking into a new and unfamilier environement:
http://www.devarticles.com/c/a/SQL-Server/How-to-Perform-a-SQL-Server-Performance-Audit/5/
January 10, 2005 at 9:44 am
This is my favorite article on Auditing new environments, it's really a must read for any SQL Server DBA.
http://www.devarticles.com/c/a/SQL-Server/How-to-Perform-a-SQL-Server-Performance-Audit/
Enjoy!
October 18, 2004 at 8:06 am
Same thing happens to me, I'd love to know why because it makes it hard to trust a solution when you can't even get the correct number of records to...
March 26, 2004 at 6:33 am
I get this also, on all five of the SQL Server installs I use. Seems to be a bug in the product.
March 5, 2004 at 6:53 am
Viewing 10 posts - 16 through 25 (of 25 total)