Viewing 8 posts - 31 through 38 (of 38 total)
You can use a strategy calling sliding window to make import and archiving faster and much easier to automate.
You can read about it here.
http://technet.microsoft.com/en-us/library/aa964122(SQL.90).aspx
June 1, 2011 at 11:27 am
That doesn't make sense.
100 GB is not too high especially depending on load and size of the database.
Just because it might be too much for the servers in your company...
May 6, 2011 at 11:07 am
I am currently setting up a clustered mirrored server on a offsite collocation for DR.
The problem with having automatic failover for mirroring is that if the principal clustered server fails...
May 4, 2011 at 3:02 pm
The problem happens when a query uses allocation scans to scan number of pages in a row, and while it is scanning another process updates or inserts records causing page...
May 3, 2011 at 11:57 am
Craig Farrell (5/2/2011)
Basically you're saying make sure my ID exists when my...
May 2, 2011 at 12:29 pm
I would leave the database at full recovery and separate the insert into smaller batches. Then perform a transaction log backup between the batches.
If you plan on going ahead...
April 29, 2011 at 11:12 am
sqlapprentice (4/28/2011)
free_mascot (4/28/2011)
Does adding additional primary/secondary file too applied on mirror?
Just tested on one of our mirrored pair, yes, the secondary file if added on principal is also added on...
April 28, 2011 at 3:10 pm
In my opinion you should work with your SQL Server DBA since performance tuning is not an easy topic to cover without having some experience with SQL Server.
Will C
MCITP, 2008...
April 28, 2011 at 12:03 pm
Viewing 8 posts - 31 through 38 (of 38 total)