If you are running the sp that executes the package within a job, then the problem could be SQL Server Agent login account.

Try executing the package from DOS with the...

If you want to access the table like this:

SELECT * FROM OSS..TableName Then SQL server will first look for the user that executed the command and then will look for...

You should't have any problem. Run sp_who2 and check for another process locking the tables that you are viewing.

Check http://oca.microsoft.com/cerintro.asp

Try creating the table like CREATE TABLE oss.w_provision.Tablename

and remember to fully reference the table when executing SELECT statements

You could in another server upgrade the SQL 7 to SQL 2000, then backup DB and restore it in your SQL 2000 production server.

Can you post the query you use ?

We also have transactional replication and never had a problem when we needed to restore the master database. Are you shure that between the master backup and the restore, you...

That option is not important to you, it only allows you to see all the options or just the basics. But if you are receiving that error message frecuently, you...

Are you sure that in the select that you use for the cursor , the last column has different values. Try printing the 3 variables inside the cursor to check.

WHILE...

You must execute:

exec master.dbo.sp_serveroption 'RPTDBPRD', 'DATA ACCESS', True

and should work fine

Can you post part of the trigger1 sintax?

You should run the OSQL command with trusted mode. (-E option). Or put what ever you want to execute on schedule into a job within SQL server.

Maybe you could move all the non primary log

with the emptyfile command and then create a new primary log with the dbcc rebuild_log command. You must ensure that no...

Can you see the backups made inside the backup device?

Check it because some one may be incomplete. Backup the dabatabase with the format option.