You'll not want to interactively query the transaction log - not a good idea.

It really depends what it is you're trying to trap. Using code is probably best - a...

If you attach through EM just ignore the log file and it will create a new log file in the same location as the mdf.

I did have an issue once...

Unless you're using adv server most of your memory will be wasted I'm afraid.

I have hazy recollections of having made various attempts to do this over the years ( very advanced fail over / dr etc. etc. ) and it didn't work.

It's something...

It will probably run faster as a proc

never seen this. increasing %age causes stats update to run longer. One point to remember is that if you have auto update stats on then the auto stats will rebuild...

Tables with sequential keys can still become fragmented.

If you have the window I'd always rebuild indexes and updates stats each night. If this is tricky then you need selective index...

tricky - out of date stats, no indexes, auto close set on database.

I usually check out the est query plan as first step with any query, then maybe test on...

can't answer your question directly but if you want to see the real i/o cost of a query always use profiler.

check your query plans, you can do this in profiler,...

have used diag manager ever since it was sql probe. It's good but I beleive the next version may be a server install which isn't so good.

Terratrax performance monitor is...

You need an additional patch if you're using awe - only problems are if you don't apply the patch.

I can add a few comments about indexing bit columns ( yes honestly !! ) One of the many features I've encountered are bit flags to say if a row...

I'm not aware of any patch problems. Presumably you must have a set of base statistics upon which to base this ?

Things to look for :-

processes running that shouldn't -...

I'd suggest you enable trace flags to write the deadlock info to the errolog so you can examine and capture the offending code.

Reads within a transaction will create locks...

W2003 supports more memory ( enterprise edition 32gb ) it also supports hyperthreading correctly and will allow 8 HT procs on enterprise ( total 16 procs )

I've not had any...