Thanks Guys, I've managed to crack it. It just needed more single qoutes, and here is the code

SET QUOTED_IDENTIFIER ON

DECLARE @srvname nvarchar(50),

  @query nvarchar(200)

SELECT @srvname='TEST123'

SELECT @query=N'' + @srvname

SELECT @query=@query + '.master..sp_msforeachdb...

I've seen this before and the only way I know is to re-create the plan.

We have all our servers running SQL with Virus check software. We only enabled scanning on incoming files, and so far no performance issues.

If optimization job was used, it would drop and create indexes table by table and in one big transaction. If anything fails, it should roll back.

Only sa can manage jobs for all of the SQL server. However,  other users who have been given access to MSDB can create their own jobs and manage them. The problem here is...

Here is another solution, that list all tables and database size.

CREATE TABLE #temp(

 rec_id  int IDENTITY (1, 1),

 table_name varchar(128),

 nbr_of_rows int,

 data_space decimal(15,2),

 index_space decimal(15,2),

 total_size decimal(15,2),

 percent_of_db decimal(15,12),

 db_size  decimal(15,2))

-- Get all tables, names, and sizes

EXEC sp_msforeachtable @command1="insert into #temp(nbr_of_rows, data_space, index_space) exec sp_mstablespace...

Are you saying the server is configured to only accept standard SQL login? if so you would need to rebuild your master databse and restore database(s) from backup. If security...

Does the userID used on the jon have access to the T drive or the file? How about creating a batch/cmd file and call these file from the dts package.

Here is a simple method to kill all processes related to a database,

declare @runcmd varchar(100), @dbconn int

declare dbconn cursor

for select spid from sysprocesses

where dbid=11 --Your database ID

open dbconn

fetch next...

Make the database suspect and restore from backup. That way SQL will not rollback.

AJ,

In EM once you start a job, you can refresh the screen to see its status. So far only Sysadmin members can see the status (Executing/Not Running).

Thanks for Steve and AJ, the problem is these guys need to check the jobs and run then in the Enterprise Manager, and as they had the SA permissions before and...

I guess there are some good points to split log file. First, it enhance the restore operation when restoring from multiple files on separate disks. Second, if you have a disk space...

Try this page, it may help you

http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B315886