I recently spent a considerable amount of time trying to do just that.  What I discovered is that SQL considers multiple transaction log files to be a single container.  You...

I certainly don't plan to be on site for the time change.  I don't even stay up on New Year's Eve!  I don't have a firm plan yet, but it...

I just spoke to my colleague about this situation.  She says that jobs which are scheduled for a specific time will be ok, but jobs that use a "frequency" type...

Be careful about adding a test user to a production database though.  Should the test user(s) have the same rights in production that they have in test?  If not, then you should...

I would have to agree with Lukas.  Although we no longer do this, part of our backup strategy used to be to stop SQL to allow the system backup to...

Even though you have a full backup, it seems that the transaction log backups can't associate with it.  Perhaps a non-logged operation has occured, or the transaction log has been...

Here's a stored procedure that I got here at SQLServerCentral.com.  I made some changes to it, which are identified with comments.  This thing works great for those stubborn logs.  Note...

I have one that creates grant/deny statements for reverse engineering the permissions.  Because of the way it works, it creates a HUGE result set.  Perhaps you could play with it to...

Lukas,

Yes, I have shrunk log files a number of times, and have never found it necessary to change recovery models to achieve it.  I did read the post and I...

If you're in Simple Recovery Mode, a backup statement is not necessary.  CHECKPOINT will commit transactions to the database, and truncate.

If you are in Full recovery mode, I would recommend...

How are you viewing the data?  For example, Query Analyzer has a default maximum number of characters per column to display in the results pane.  I'm not sure what the default...

By the way, if that update count is useful to you, you can put it back in. The 01000 message doesn't hurt anything at all.

Steve

Again, its not an error message.  Its like an "aknowledgement" that SQL is preforming a print command.  Anytime you put a PRINT command in a stored procedure, you're going to...

You can change the growth increment in Database properties in EM to whatever you like.

Steve

Thats not an error.  SQL adds that at the end of a print line.

It looks like you have something like 

PRINT 'UPDATING: " + cast(@count as varchar(3))

in your stored procedure.  Nothing to...