http://blogs.msdn.com/bartd/archive/2006/09/09/Deadlock-Troubleshooting_2C00_-Part-1.aspx

Note there are 2 additional parts to this blog series.

There are at least 2 things you should do before even considering that trace flag.

1) look for unnecessary temp object creations. There could be lots of causes...

The clustered index thing could actually make a HUGE difference, despite the no where clauses. HEAPS can wind up with a bajillion forwarded records which will crush the server...

1) did you update ALL statistics with a FULL SCAN?

2) I would simply use profiler to capture rpc batch completed and tsql batch completed events and find the big hitters....

I have done this type of processing for at least 15 years, probably more. Works fine, lasts a long time! 😎

It is a simple trigger...

Forget partitioning for now. With no experience in it you will be just as likely to mess something up as not since it is a VERY complex subsystem.

For the...

Depending on how many tables you have I would also look into having the triggers simply put the primary key for each table into a table that is used to...

Just had a client hit me up today with a need for RLS - with a twist. The "owner" of the record always has access and that owner can...

What you are looking to do is known as Row Level Security, and it is a certified BITCH to do in SQL Server. There is no easy/efficient way to...

1) Who cares how long it takes to create a database? How often is that done, and how many of THOSE times does it need to complete 15 seconds...

http://www.sqlskills.com/blogs/paul/sql-server-2008-filestream-performance/

http://www.sqlskills.com/blogs/paul/high-performance-filestream-tips-and-tricks/

Third party apps have been the cause of TREMENDOUS grief for clients over the years!! Backup, "management" apps, antivirus (LOTS of issues!!), etc...

mealies (3/22/2013)

---

The execution plan wasn't pretty but no missing indexes reported. Although the SSMS toolkit plugin warns the query plan takes 5mb of space.

Looked into the SQL stack dumps...

Given that you are shipping across the internet I would encrypt my backup too. that you cannot do with SQL Server built-in stuff. Either get third party tool...