Ok if I use the raw backup files without trimming the file names I STILL can an error...I am banging my head against the wall on this....

Here is my script...

I have a script that strips the datetime off the file before restoration. This works fine on the full backup database restore.

Here it is for differential

/* Unzip SmartStream...

More information to assist

SQL Server 2005 SP2 Standard Edition

Databases are set to 80 compatibility (as per the vendor)

Sorry here is the backup code

DECLARE

@SQL nvarchar(300),

@date varchar(20)

SET @date = REPLACE(CONVERT(varchar,GETDATE(),101),'/','')

SET @SQL = N'

BACKUP DATABASE DBSallc

TO DISK = ''\\[servername]\SQLBACKUP$\[servername]\Data\DBSallc' + @date + '.bak''

WITH FORMAT

RESTORE VERIFYONLY FROM DISK =N''\\[servername]\SQLBACKUP$\[servername]\Data\DBSallc'...

ALTER DATABASE DBSallc SET single_user WITH ROLLBACK IMMEDIATE

RESTORE DATABASE DBSallc from disk =

'E:\SQL Backup\Data\DBSallc.bak' WITH REPLACE,

MOVE 'DBSallc_data' TO 'D:\Data\DBSallc.mdf',

MOVE 'DBSallc_log' TO 'E:\DataLog\DBSallc.ldf',

NORECOVERY

RESTORE DATABASE DBSallc from disk =

'E:\SQL Backup\Diff\DBSallc.bak' WITH REPLACE,

MOVE...

Thanks...I was going that route my only concern is that xp_cmdshell will only error if it cannot fire off the .bat file not properly executing the command within the .bat...

Ugh...Ken thanks that formats it correctly but now the script will not run. Altering the quotes causes the file renaming to not work.

If I take this text and run...

One more thing i cannot find it but does anyone know the parameter for unzip to not extract the results into their own folders?

Here is my final code I would like a second pair of eyes...

DECLARE db_cursor CURSOR READ_ONLY FOR

SELECT name FROM sys.databases

WHERE name NOT IN ('master','tempdb','model','msdb')

OPEN db_cursor

FETCH NEXT FROM db_cursor...

No that would be too easy.... unfortunately 98% are 7 characters but two are not. One is 9 (DBSCOMMON) and one is six (RevRec)

I am working with this shell...

Unfortunately I have not...and I cannot reinstall as...

Sorry my examples were not clear I meant to say 'Log into the Server where SQL server resides'

I understand the difference I am just going through our change management to...

rbarryyoung (10/14/2008)

---

jsheldon (10/14/2008)

---

yes to both of your questions...the SQLProxy account is valid and able to log on to the server, my domain account is a sysadmin rights on the SQL...

rbarryyoung (10/14/2008)

---

jsheldon (10/14/2008)

---

rbarryyoung (10/14/2008)

---

Two questions:

1) Does the '##xp_cmdshell_proxy_account##' credential exist? If so, what is it?

2) What...

rbarryyoung (10/14/2008)

---

This paragraph from BOL pretty much sums up the situation:

xp_cmdshell Proxy Account

When it is called by a user that is not a member of the sysadmin fixed server role,...