Somethign to be aware of: With 64-bit servers, if you have plenty of memory to spare, there is no problem leaving the SQL memory setting at the...
Sorry Satya, but I still hate DTA. It suggests way too many indexes, generally with far too many key columns and covering columns, which if you...
Certainly. With PUSH replication, you require a distribution agent for each publication per subscriber. e.g. 5 publications with 5 subscribers =...
Exactly. Like I said : ".... might still have been relevent to other people who hadn't considered it....." So the answer was "Yes".
I'm sorry, but that's possibly the worst, most mis-leading advice I've seen in a long time. I've had a look at the recommended "recovery...
I had noticed that - but the idea of using partitioning might still have been relevent to other people who hadn't considered it, so I thought it was...
It is not necessarily the case that you should create as many tempdb data files as you have CPU cores. Whilst having multiple files can be helpful...
Are you using Enterprise edition? If so, have you thought of using partitioned tables to switch the archive data out of the ProcessData table and...
Personally, I'd be very cautious about using the Tuning Advisor. It frequently gives very careless recommendations, and it's not uncommon to see...
Just because the 2 databases are replicated does not mean that the indexes need to be identical (I'm assuming you do mean replication and not log...
Sadly, no - because you don't say what the actual query is. Also, we'd need to see the table and index strctures in more detail, together with some...
The addition of "dbo" into the SP name was a "feature" if you used the SSMS GUI to create replication under SQL2005. Basically, this was a bug,...
It's worth pointing out, though that PULL replication is much more scalable than PUSH replication.
Separate names with a comma.
