SELECT NEWID(), name, ROUND(RAND(object_id)* 1048576, 0), GETDATE() FROM sys.columnsĪLTER TABLE dbo.NoddyTable ADD CONSTRAINT PK_NoddyIDĬREATE NONCLUSTERED INDEX IDX_NoddyName_NoddyDate SELECT NEWID(), name, ROUND(RAND(object_id)*856542, 0), GETDATE() FROM sys.columns NoddyID UNIQUEIDENTIFIER NOT NULL DEFAULT NEWID() IF OBJECT_ID('dbo.NoddyTable', 'U') IS NOT NULL
( NAME = N'Corrupt2K8_log', FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\Corrupt2K8_log.ldf' , SIZE = 524288KB, MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB ) ( NAME = N'Corrupt2K8', FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\Corrupt2K8.mdf' , Let's start with actually creating the database, this is done with the following T-SQL codeĭon't forget to modify any drive letters and paths before executing the script 😉 We're going to use a simple script and go through it in stages, with diagrams, to see what's happening. I use the popular XVI32, it's free of charge and requires no installation, unlike some other editors that are available. The tools to use here are pretty simple, to create the corrupted database you will need an instance of SQL Server and a Hex editor.
Now, you could trawl the internet looking for them or you could try to create them yourself but how exactly do you corrupt a database intentionally and still get to be able to bring it back online afterwards! 😉įor this we need to dig in a little into the SQL Server database file structure.
This article will seek to detail how to go about creating a corrupted database which you can readily attach to your SQL Server instance. It's quite possible that at some point you would want to have a corrupted SQL Server database to use for checking your maintenance scripts or sanitising and practising your disaster recovery techniques (we all perform DR tests at regular points, right!).
0 kommentar(er)
