And change the data types so that you're storing date and time as date and time. Same thing goes for any other data type.

Not a clue how to address your specific issue, but, one HUGE point.

The GUI for Profiler has a different memory management mechanism within SQL Server than the server-side...

You can only get that information if you are gathering query metrics in some fashion. Since you're posting in a 2008 forum, the general method for this is to use...

When thinking about performance of the database, two things should drive your processes. First, you only get one clustered index and it defines data storage. Therefore, the most common path...

Here's the fix I used. Seems to work well.

Partly joking of course. Partly.

Personally, I think I'd look to split the customers by database rather than try to put them all in one. You've hit the real issue that's going to be brutally...

Without using log shipping or replication or availability groups (all of which you've dismissed), I don't know of any way you can easily move only the data that has changed...