Moving system files means moving system databses or sql binaries?

BOL topic "moving system databases"

http://msdn2.microsoft.com/en-us/library/ms345408.aspx

How to move SQL Server databases to a new location by using Detach and Attach functions...

Only option I have seen is if you GRANT ALTER permission to the user he can see the text but can't execute...

ALTER permission is dangerous

Depends on how you have the backup of dts.

If you have dts as .dts file use EM....

you can't overwrite a package.. you have to delete or rename the package before...

What notification drop down box? Is it related to db mail or notification services?

You can check the Database Mail Log..

Check BOL topic "Database Mail Views"

http://groups.google.com/group/microsoft.public.sqlserver.server/browse_thread/thread/7f80428fbc46c8eb/ef03601f6db6487d?lnk=st&q=sql+server+2005+log+file+maxsize+issue&rnum=1&hl=en#ef03601f6db6487d

Some times you need to fool SQL server to resolve the issues...

Thanks for the feed back

Yes you are right...

If the plan and data is cached SQL serve your request from cache/memory, so it doesn't need to work much on the request...

Use OSQL or SQLCMD command with cursor or while loop...

SELECT 'EXEC XP_CMDSHELL "OSQL -S'+@@servername+' -d '+NAME+' -i c:\triggerfile' FROM MASTER..SYSDATABASES WHERE DBID >6

Take the output from the above command...

Your logshipping is still enabled where as your jobs, alerts and restores disabled manually...

I think there is not an option to disable (not sure) but there is an option to delete...

Last night I tried diffent ways without success...let us see if any one comeup anthing...

Can you post the exact error he is getting.

Are you both tried the same table and same column update? Reason could be some constraint voilation.

This procedure cann't be used with windows logins...

If there is nothing to report it will give you nothing...

May be you don't have orphand logins in your db.

I don't have the script handy but you can use the following table get the information...

select * from sys.tables

select * from sys.indexes

sp_helpindex [schema.tablename]

see BOL for more details...

You can use RESTORE HEADERONLY command to get the details..

See BOL for more details...

Write the job out put file to a file and see what is happenning.

At the same time you can run the profiler also with error events.