use datediff(dd, InsertDate, '1/22/3004) in where clause instead.

It does have negative impact on server load.

You can kill aged connections by query sysprocesses, there are login_time and last_batch columns to serve your purpose.

use set dateformat to specify date format before loading

dateformat could have mdy, ydm or ymd. Check book-on-line for detail.

It is a cross session issue.

Following code demo for that

declare @sqlst varchar(1000)

set @sqlst = 'declare @tbl table (au_id varchar(11));insert @tbl select au_id from authors;select * from @tbl'

exec (@sqlst)

suspect network connection issue.

Make sure both client and server support the same network protocol.

In case of IP,

check if you can ping your server.

or change server name to ip address and...

The added new field has to be not null with default value.

convert total duration to seconds.

use dateadd and convert function with 108 style to get HH:mm:ss, then use datediff to get days.

Here is sample.

declare @sec int

declare @base datetime

select

sp_helpuser

I've done it, and it works.

Log file(s) growing rate is a good indicator.

A computed column can be spedified by one unit of calculation. It could be one of seconds, minutes, hours, days and years.

You can achieve any formt by using datediff function...

check sp_dboption autoclose.

It is designed for lapton with limited resource. It costs in performance as usual.

It sounds like a permission. Run it directly from server fail proves that.

Server might not have right back to local poxpro table.

If it is part of transaction (use MSDTC). Then the literature applies.

Backup log using sqlmaint, it prives cleaning up mechanism and naming convention.

Scheduled script to copy log files across and restore it.

In the event of error(warning), CDO mail is an option.

The...