oops, missed the bit that mentioned only 2 transaction log backups a day, I'd go with one every hour on a production system.

Hi Sam,

We use SQLCompare by RedGate and find that it does an adequate job for this type of thing.

Mike

Hi Deep,

If I understand your question it's regarding the physical size of the transaction log files as opposed to the size of the transaction log backups generated.  It's good that...

You could also create the stored procedure in the master database with the SP_ prefix and set it as a system object, that way regardless of where you ran it...

Hi there, to be honest the best method from what you've said is to dump the database to disk and then back that up to tape (or if you have...

That's probably because licensing is such a pain that most good DBA's manage to offload the responsibility onto someone else, that way freeing them from the burden and allowing them...

Hi John,

This doesnt sound to far wrong to tell the truth, when you do a restore to a new server/database the first thing that gets done is that the data...

I think the word you're looking for is IFilter, we currently make use of various different ones to allow us to search documents (PDF, DWG, PLT, ZIP to name but a few)...

I've seen it before where a query from a remote server doesn't use the approriate index when executing, mind you, that was a year ago on a SQL 7 box so...

dbcc checkdb (DBNAME) with tableresults

it's a simple as that.

Also, i found the place that i'd seen it, it's hidden away in the DBCC SHOWCONTIG bit of BOL, so i guess...

in a former company we occasionally encountered problems where the transaction log didn't expand automatically even though it was set to.  This is the only time that i've ever had...

i'm sure this is documented in BOL? we've used this method for over a year now and it sure makes things easier to examine long term.

No idea as of yet, but to be honest even if it was today i'd want to wait at least 2 months before applying it on our production systems.

We don't...

We tend to disable our transaction log backups during full and differential backups (also reindex jobs and DBCC checks), but that's mainly due to a set of jobs we have...

That's why people should always add the projected size of their largest table to the projected database growth when looking at capacity planning for their systems.

We've been stung like this...