Could you show us what LogUserActivity does?

Does the the app that uses this DB use Connection Pooling?

The reason you've got as difference is because of the number of rows.

The 2 day query is returning 42k rows and that number is (probably just) small enough that SQL...

What comes to mind is using xp_readerrorlog to get the log, then looking for the line that reads

It seems to be there whether the...

Take a test server, take baseline readings of the CPU usage, IO usage, etc. Implement some traces, take new readings.

If you're running SQL 2005, you already have a serverside trace...

Sure. Works in 2005 just fine

DECLARE @TimeStamp VARCHAR(4)

SET @TimeStamp = REPLACE(CONVERT(VARCHAR(10),GETDATE(),108),':','')

EXECUTE ('CREATE DATABASE TEST_DB' + @TimeStamp + ' ON

( NAME = TEST,

FILENAME = ''C:\SQL2005\Snapshot\TEST_DB' + @TimeStamp ...

Ok, you could try something like this (replacing placeholders with pertenant values)

Provider=sqloledb;Data Source=myServerAddress;Initial Catalog=myDataBase;

User Id=myUsername;Password=myPassword;

What version is your SQL Server (run SELECT @@Version)

Can you connect from query analyser using the...

Do you have the log file as well (ldf). If not, you'll have to use the attach_single_file proc and hope that the DB was shut down cleanly.

Much lighter than profiler. Make sure that the trace is writing to a fast drive that does not contain your database's data or log files or tempdb.

You'll get used to it in time. There's no quick solution. For now, it's up to you to make sure...

Firstly, don't ever, ever, ever, ever use the sa account for an application's login. You're asking for security problems.

Create an account just for the application that has just the permissions...

Have you done any index rebuilds lately?

Rather stay away from shrinking. Often you shrink the file and the next thing sQL needs to do is grow it again. It can...

Have you tried it?

Unless...

Oh sure.

The 'hit recursion limit and roll back' was based on the assumption that there's no 'escape clause', that the trigger's been written to recurse 'forever'

By default triggers cannot fire themselves. (recursive triggers disabled) so 2 rows will go in, but the second won't fire the trigger

If you have recursive triggers enabled then the trigger...

You didn't miss anything. DTA has a very bad habit of massively over-suggesting indexes and statistics. Take its suggestions with a large pinch of salt.

I would suggest that you try...