RESTORE FILELISTONLY data types

I've been having trouble guessing the data types for the result set of the RESTORE FILELISTONLY result set. Can anyone shed some light on this?

I'm not using all of the columns, so I defaulted to VARCHAR(100) when I wasn't sure. Here are my guesses:

CREATE TABLE #files &#40;
	LogicalName				VARCHAR	&#40;256&#41;
	,PhysicalName			VARCHAR	&#40;512&#41;
	,Type					VARCHAR	&#40;10&#41;
	,FileGroupName			VARCHAR	&#40;100&#41;
	,Size					VARCHAR&#40;100&#41;
	,MaxSize				VARCHAR&#40;100&#41;
	,FileID					BIGINT
	,CreateLSN				VARCHAR&#40;100&#41;
	,DropLSN				VARCHAR&#40;100&#41;
	,UniqueID				VARCHAR&#40;100&#41;
	,ReadOnlyLSN			VARCHAR&#40;100&#41;
	,ReadWriteLSN			VARCHAR&#40;100&#41;
	,BackupSizeInBytes		VARCHAR&#40;100&#41;
	,SourceBlockSize		VARCHAR&#40;100&#41;
	,FileGroupID			VARCHAR&#40;100&#41;
	,LogGroupGUID			VARCHAR&#40;100&#41;
	,DifferentialBaseLSN	VARCHAR&#40;1000&#41;
	,DifferentialBaseGUID	VARCHAR&#40;100&#41;
	,IsReadOnly				TINYINT
	,IsPresent				TINYINT
&#41;

SET @SQL = N'-SQL "RESTORE FILELISTONLY FROM DISK = &#91;C:\db.sqb&#93;" '

INSERT INTO #files
EXECUTE MASTER.dbo.sqlbackup @SQL

Thanks,
- Matt

matt.stanford November 29, 2007 08:37

Comments

2 comments

The data types are identical to that returned by the native RESTORE FILELISTONLY command (see here), except for the following:

- UniqueID, LogGroupID and DifferentialBaseGUID are varchar(36) instead of GUIDs

- IsReadOnly and IsPresent are integers instead of bits

The reason for the discrepancy is because the SQL Server extended stored procedure library does not support GUID and bit types.

petey November 29, 2007 10:45

0
Very nice. Thank you.

-Matt

matt.stanford November 29, 2007 13:03

0

Add comment

Please sign in to leave a comment.

How can we help you today?

RESTORE FILELISTONLY data types

Comments

Add comment