Instead of dynamic SQL, I recommend conditional execution like this:

alter proc Test_SP

@dbName Sysname

As

if @dbName = 'Database1'

begin

select * from Database1.dbo.TableName

end

else if @dbName = 'Database2'

begin

select * from Database2.dbo.TableName

end

Go

2- Re-indexing / integrity checks then backup databases

No point in taking backup of currupt database.

select distinct s2.ServerName, s2.DateFrom, s2.DateTo

from dbo.Server s1

inner join dbo.Server s2

on s2.ServerName = s1.ServerName

where s2.DateFrom >= s1.DateTo

union

select s.ServerName, s.DateFrom, DateTo

from dbo.Server s

inner join (

select ServerName, Min(DateFrom) DateFrom

from dbo.Server

group...

select

(select count(*) customer where )

(select count(*) booking where )

(select count(*) invoice where )

(select count(*) commission where )

Thanks Steve, for the information about recovery.

See the query execution plan. Create suitable covering index.

The TIMESTAMP data type of SQL Server is not equivalent to DATETIME.

It is equivalent to BINARY(8).

Since this is a production server, DETACH option may not be suitable, as it makes the database OFFLINE.

Use STOPAT clause in the RESTORE statement to restore to a point in time.

It looks like in the trigger is trying to insert xml data into a column. However the length of the column is too small to hold the xml data. Therefore...

For moving use databases there are two options:

1) detach/attach

2) backup/restore

All other versions support job scheduling.

You are right. You can run a query as a job.

Minimun 1 minute.

Inteactive logon restriction does not impact SQL Server.

Becuase SQL Server is a service.

Services don't need interactive logon previlage.

Welcome.

Use "Maintenance Cleanup Task" to delete older .bak files.

Maintenance Plan automatically adds date time stamp to the filename.

e.g. master_backup_200711132245.bak