the server is dedicated server, no SSRS, no SSIS, no SSAS running.

thank you. I got it.

GSquared (9/26/2012)

---

For example, I've set up scripts that would check the current LSNs vs the last ones backed up, and customize which databases to back up based on that....

I deleted this replication and recreated from the scatch. It works now.

if the user exists in the DB which you just restored,

you can schedule a job to run this after you restore DB

EXEC sp_change_users_login 'update_one', @username, @username

Or you can use this sql query to get backup audit,

select * from ::fn_trace_gettable('DefaultTraceFolder\log_601.trc',default)

where textdata like '%backup%' and textdata is not null

From default trace, you will find backup information, including Who, when, where and which database.

Go to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG,

Defaule file name like log_xx.trc.

Our company has upgraded SQL 2000 to SQL 2005 long time ago without these questions' answers.:)

I had a similiar experience. SQL logins had no problem to connect to SQL. only one Windows Logins could connect, other not.

Drop server and add server did help on...

Can you try to drop server and add server back?

Sp_dropserver @Servername

Sp_addserver @Servername,local

To find backup size for Every DB

select database_name,backup_size,backup_start_date from msdb.dbo.backupset

order by database_name

Can you check server date time setting? It might be wrong server date time.