![]() We back up the database, without the file stream like this: BACKUP DATABASE FileStreamDB We have this almost working as we'd like. ![]() In those cases, we are rarely interested in the files stored in Binar圜ontent (now using FILESTREAM). With everything residing in the PRIMARY file group, except the field FileBinar圜ontent which is in a separate file group FileStreamContentFG.įrom a developer's point of view, we would often like a fresh copy of the database from our production environment, to be able to work the the latest data. ADD CONSTRAINT DEFAULT (newsequentialid()) FOR The Binar圜ontent table looks roughly like this: CREATE TABLE. We did the necessary modifications to our database without any problems, and our system is still working fine after the migration. Recently we've been testing the possibility to move all these files out of the database to the file system using FILESTREAM. As the name suggests, this is a table where we store simple files, of any kind, directly in the table as a BLOB. Out of these, approximately 8.5 GB is in a single table Binar圜ontent. ![]() The total size of the database is about 12 GB. It is an MS SQL database running on SQL Server 2008 R2. We are developing a system with a large-ish database in the bottom.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |