can you run sp_updatestistics and dbcc updateusage(0) with count_rows ?

This should get you fresh stats ...

starting a SQLTrace will also help to determine the source of your deletes.

bring on the caffeine.

We have a volume licensed Dev Edtn.

Also keep in mind, if you don't supply a key, it will install a Ent edtn for 140 days.

You can off course create a trigger for delete on that table to perform a rollback for delete statements and raise en error stating all connection info.

did you check out backup compression softwares ?

They typically reduce the size to +/- 20%

there is off course the undocumented :crazy: [sp_MSforeachtable].

Keep in mind the order of execution if you have DRI.

(or repeat more than once)

If you want to avoid log overhead, try to...

use an insert/update trigger to check the condition and rollback if invalid.

Before you start the restore to recover PIT, you should still backup the current log of the db !

After that, you can restore your previous full backup ( PIT,...

btw

did you check the plan using a @variable in stead of the hard coded

Maybe vendorid 14 just generates a less optimal (non...

A trace file does not switch by day.

run

SELECT * FROM ::fn_trace_getinfo(default)

If you don't see an active trace, someone did disable the default trace for your instance.

There are...

did you check Kimberly's very good white paper on partitioning ?

http://msdn2.microsoft.com/en-us/library/ms345146.aspx

BOL also has some info on sliding windows:

- "Transferring Data Efficiently by Using Partition Switching"

- "Designing Partitions to Manage Subsets...

I would alter the distinct to a group by on all columns.

Group by may take advantage of existing indexes.

what's the size of your indexes (pages) ?

seems to me like your data after exp is a date, so make it a datetime column !

pro:

- only date(time) values accepted

- the whole bunch of datetime related functions

con:

- no...

the original queries contained this where clause:

U.[user_id] = @original_user_id AND

U.[user_name] = @original_user_name AND

U.[user_surname] = @original_user_surname AND

...