Restore script not working

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » SQL Server 2008 - General » Restore script not working

15 posts, Page 1 of 2

1 2 »»

Restore script not working

Rate Topic

Display Mode

Topic Options

Author

Message

cor_perlee

Posted Wednesday, January 11, 2012 8:22 AM

Grasshopper

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 5:16 AM
Points: 13, Visits: 161

Hi all,

I have been working on this script all day trying to get it to work.
Just can't figure it out. There are no error messages but nothing happens.
The script was copied of the internet and adjusted for my purposes. I have a large number of database that will have to be created soon. All I will get is a folder with a llot of backupfiles and possibly a list with databasenames .

Any help would be greatly appreciated,

-- Use VARCHAR as the restore statement doesn't like NVARCHAR
DECLARE
@data_file_path VARCHAR(512)
, @data_file_1_path VARCHAR(512)
, @log_file_path VARCHAR(512)
, @backup_path VARCHAR(512)
, @backup_extension VARCHAR(4)
, @mdf_extension VARCHAR(4)
, @ndf_extension VARCHAR(4)
, @ldf_extension VARCHAR(4)

-- ** VARIABLES THAT MUST BE SET **--
SET @data_file_path = 'D:\Data\'
SET @data_file_1_path = 'D:\Data\'
SET @log_file_path = 'D:\Logs\'
SET @backup_path = 'D:\Klantenmap\'
-- **----------------------------**--
SET @backup_extension = '.bak'
SET @mdf_extension = '.mdf'
SET @mdf_extension = '.ndf'
SET @ldf_extension = '.ldf'

DECLARE @DATABASES_TO_RESTORE TABLE
(rownum int IDENTITY (1,1) PRIMARY KEY NOT NULL,
backup_name VARCHAR(64),
restore_as VARCHAR(64));

-- ** Declare the Databases to be Restored ** -- INSERT INTO @DATABASES_TO_RESTORE
SELECT '25000994', '25000994'
UNION
SELECT '25001905', '25001905'

-- ** -------------------------------------** --
DECLARE @max_rows INT, @row_count INT
SET @row_count = 1
SELECT @max_rows=count(*) FROM @DATABASES_TO_RESTORE

WHILE @row_count <= @max_rows
BEGIN

DECLARE
@backup_name VARCHAR(32)
, @restore_as VARCHAR(32)
, @logical_data_name VARCHAR(64)
, @logical_data_1_name VARCHAR(64)
, @logical_log_name VARCHAR(64)
, @data_file_full_path VARCHAR(512)
, @data_file_1_full_path VARCHAR(512)
, @log_file_full_path VARCHAR(512)
, @full_backup_path VARCHAR(MAX)
, @cmd VARCHAR(128)
SELECT
@backup_name = backup_name,
@restore_as = restore_as
FROM @DATABASES_TO_RESTORE
WHERE rownum = @row_count
SET @full_backup_path = @backup_path + @backup_name + @backup_extension

DECLARE @filelist TABLE
(LogicalName NVARCHAR(128) NOT NULL,
PhysicalName NVARCHAR(260) NOT NULL,
[Type] CHAR(1) NOT NULL,
FileGroupName NVARCHAR(120) NULL,
Size NUMERIC(20, 0) NOT NULL,
MaxSize NUMERIC(20, 0) NOT NULL,
FileID BIGINT NULL,
CreateLSN NUMERIC(25,0) NULL,
DropLSN NUMERIC(25,0) NULL,
UniqueID UNIQUEIDENTIFIER NULL,
ReadOnlyLSN NUMERIC(25,0) NULL ,
ReadWriteLSN NUMERIC(25,0) NULL,
BackupSizeInBytes BIGINT NULL,
SourceBlockSize INT NULL,
FileGroupID INT NULL,
LogGroupGUID UNIQUEIDENTIFIER NULL,
DifferentialBaseLSN NUMERIC(25,0)NULL,
DifferentialBaseGUID UNIQUEIDENTIFIER NULL,
IsReadOnly BIT NULL,
IsPresent BIT NULL,
TDEThumbprint VARBINARY(32) NULL)

INSERT into @filelist
EXEC ('RESTORE FilelistOnly FROM DISK = ''' + @full_backup_path + '''')

IF @@ROWCOUNT = 2
BEGIN

--SELECT @logical_data_name = LogicalName FROM @filelist WHERE [Type] = 'D'
--SELECT @logical_log_name = LogicalName FROM @filelist WHERE [Type] = 'L'
SET @data_file_full_path = '@data_file_path' + '@restore_as' + '@mdf_extension'

SET @data_file_1_full_path = '@data_file_1_path' + '@restore_as' + '@ndf_extension'

SET @log_file_full_path = '@log_file_path' + '@restore_as' + '@ldf_extension'

RESTORE DATABASE @restore_as
FROM DISK = @full_backup_path WITH FILE = 1,
MOVE N'U4S33_Data' TO @data_file_full_path,
MOVE N'U4S33_Data1' TO @data_file_1_full_path,
MOVE N'U4S33_Log' TO @log_file_full_path

END

ELSE
PRINT 'CANNOT RESTORE DATABASE ' + @restore_as + ' THE BACKUP CONTAINS MORE THAN 1 BACKUP SET'
SELECT @row_count = @row_count + 1
END

Post #1234029

Dev

Posted Wednesday, January 11, 2012 8:35 AM

SSCrazy

Group: General Forum Members
Last Login: Wednesday, May 15, 2013 2:05 PM
Points: 2,013, Visits: 1,566

Usually, we backup all databases with a script. Restore is usually per database (as on need). Why do you want to restore all databases? How many databases you need to restore with this script?

Copying from blogs & running it blindly on PROD server is very dangerous. Test your scripts on Test Server first.

~Dev~

Post #1234041

cor_perlee

Posted Wednesday, January 11, 2012 8:44 AM

Grasshopper

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 5:16 AM
Points: 13, Visits: 161

Hi,

The databases are for a cloud invironment.
Al large number of customers will have to be created on the databaseserver.
The customerdatabases will be delivered as .bak files.

Cheers,

Cor

Post #1234050

Dev

Posted Wednesday, January 11, 2012 8:55 AM

SSCrazy

Group: General Forum Members
Last Login: Wednesday, May 15, 2013 2:05 PM
Points: 2,013, Visits: 1,566

If it’s less than 20, I would still prefer writing individual restore commands else your approach.

~Dev~

Post #1234065

cor_perlee

Posted Wednesday, January 11, 2012 8:57 AM

Grasshopper

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 5:16 AM
Points: 13, Visits: 161

Actually it os somewhere between 300 and 700

Cheers,

Cor

Post #1234067

Dev

Posted Wednesday, January 11, 2012 9:08 AM

SSCrazy

Group: General Forum Members
Last Login: Wednesday, May 15, 2013 2:05 PM
Points: 2,013, Visits: 1,566

Now I agree with your approach.

Please add a PRINT statement in IF block for debugging and post the results.

IF @@ROWCOUNT = 2

~Dev~

Post #1234082

Grant Fritchey

Posted Wednesday, January 11, 2012 9:12 AM

SSChampion

Group: General Forum Members
Last Login: Today @ 6:44 PM
Points: 13,381, Visits: 25,173

Looking at the restore command itself, logically it makes sense. You're going to have to break down & issue print statements to validate that everything is working. Instead of trying to run the restores, just issue a select statement so that you see all the data coming back and you can ensure that it's correct to fill in the properties for the restore statement. Then try using the data in a single restore statement. Nothing is jumping out as being especially problematic.

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software

Post #1234089

cor_perlee

Posted Wednesday, January 11, 2012 9:16 AM

Grasshopper

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 5:16 AM
Points: 13, Visits: 161

Hi ,

Actually I added serveral ' print step(n) ' to the script to see how far it would go.

It stops short of this part:

-- ** -------------------------------------** --
DECLARE @max_rows INT, @row_count INT
SET @row_count = 1
SELECT @max_rows=count(*) FROM @DATABASES_TO_RESTORE

The piece that procedes it works just fine.
SELECT '25000994', '25000994'
UNION
SELECT '25001905', '25001905'

A select on the temporary database shows the values.

But after this nothing is printed anymore despite the print statements that follow.

cheers,

Cor

Post #1234099