Got the answer from some expert. This just confirms that the sql version > 7.0.

This is not my sp. These are the replication system sps. I don't understand why the version is validated everytime...

Another crude method

select client_name,phone

from(

select temp.client,phone

from

(select [client],max(DATEs) datephone

from contact

group by client)temp

inner join contact

on contact.client = temp.client

and contact.dates = temp.datephone)tmp

inner join client

on client.client_id = tmp.client

Please elaborate your question

another way

select sqlserver_start_time from sys.dm_os_sys_info

Actually i tried some common dmvs but don't know how to get the value of mirroring timeout and mirroring heartbeat. I know we can change this as follows:

ALTER DATABASE <dbname>...

can't run the script

Msg 55555, Level 16, State 1, Procedure sp_MSforeach_worker, Line 92

sp_MSforeach_worker assert failed: command too long

The sql service must be started after msdtc is started.

try xp_cmdshell 'sc start MSDTC'

This is something really new in SQL 2008 sp2. I shall verify the BOL and let you know if i find anything.

Tweak the query timeout

This value 684991 is not changing. This connection used this much cpu time that time only.

AFAIK the log files are filled up sequentially. I believe following scenario in your case.

1. There are three log files ie LF1, LF2 and LF3

2. LF1 filled up.

3. LF2 started...

try this

BEGIN TRAN test

DELETE tablename

FROM (SELECT Column

FROM

(

SELECT column/s, row_number() over(ORDER BY getdate()) as r

...

Even 16 TB is going to be very heavy. Please look into other stats b4 proceed with a huge data.

-Lucky