I highly recommend ApexSQL Log and Recover.

Disclaimer: I have a close relationship with Apex, use their products and recommend them to my clients. Also, if you...

cfradenburg (3/2/2010)

---

You should also keep in mind that if one auto grows that SQL will no longer balance the load across the different files properly. Our recommendation to our...

Could well be a memtoleave problem, since you are 32bit. -g startup parameter can be used to increase this. You may wish to get a professional involved to...

Who is this Codd character?? Probably someone related to that Celko character! :w00t:

I wouldn't sweat that - you are certainly not alone!...

Not true!! I am actually a great fan of it and use it where appropriate, which is far more often...

1) I advise my clients to avoid NetApp stuff like the plague when dealing with SQL Server servers. Way too many problems historically

2) I have several clients very heavily...

Probably some language barriers here, but it sure sounds like you need an expert to review your maintenance practices, ASAP.

1) No GUIDs as PKs for me please, sequential or otherwise

2) I am with another poster on OrderDetails: OrderID + Sequential Line Number as PK...

cjones-956169 (2/26/2010)

---

From the perfmon counters, it looks like you are doing 1 insert per transaction.

Transactions / Sec : 1921 ( For SQL Database)

Would it be possible for you to batch...

The only reliable way is to have ABSOLUTE control over all sourcecode that is EVER executed against...

I would imagine that even SELECT ... (NOLOCK) would take a SCHEMA LOCK that might prevent/be blocked by this type of activity. Important question is why were you trying...

Be VERY careful with the 'recommendations' that DTA spits out at you. They can truly devastate your database. WAY too many indexes and WAY too many INCLUDED columns....

2000 record per second steady state capabilities is reasonably high, even in today's world. There are MANY things that can cause your throughput to fluctuate, chiefly among them are...

I wouldn't recommend SELECT * without a WHERE clause for this because it could bring back billions of rows of data. SELECT TOP 1.. will suffice with the TABLOCKX...