The Art of SQL Server FILESTREAM - Red Gate Software

Chapter 7: FILESTREAM Database AdministrationUSE NorthPoleGOCREATE TABLE [dbo].[Items]([ItemID] [int] IDENTITY(1,1) NOT NULL,[ItemGuid] [uniqueidentifier] ROWGUIDCOL NOT NULL UNIQUE,[ItemNumber] [varchar](20) NULL,[ItemDescription] [varchar](50) NULL,[ItemImage] [varbinary](max) FILESTREAM NULL,CONSTRAINT PKEY_Items PRIMARY KEY CLUSTERED([ItemID] ASC))Listing 7-19:Creating a FILESTREAM table.This table is a bit different from the previous examples; this time, the Items table has anIDENTITY column called ItemID, which has a PRIMARY KEY defined on it. The next stepis to insert a few rows into the table (Listing 7-20).INSERT INTO Items(ItemGuid, ItemNumber, ItemDescription, ItemImage) VALUES(NEWID(), 'ITM001', 'Item 1', 0x),(NEWID(), 'ITM001', 'Item 1', 0x)Listing 7-20:Populating the table with zero-length files.In this simple example, there will only be two files in the FILESTREAM data container.However, imagine that the database has grown very large and the folder contains a largenumber of FILESTREAM data files, necessitating the move of the FILESTREAM filegroupto a new disk volume. For the purpose of keeping this example simple, let's assume thatthe new location is C:\ArtOfFS\Demos\Chapter7\NorthPole_fs2. Of course, inreality, the new location would be on a separate disk volume.The approach we will take here is to add a new FILESTREAM filegroup at this newlocation, and rebuild the clustered index on the FILESTREAM table, which will move theFILESTREAM data to this new location. Listing 7-21 adds a new FILESTREAM filegroupinto the NorthPole database.296