meta user
network profile
| bio | website | stackoverflow.com/users/… |
|---|---|---|
| location | Norway | |
| age | 30 | |
| visits | member for | 1 year |
| seen | Mar 7 at 7:18 | |
| stats | profile views | 1 |
Apprentice Software Craftsman
|
Mar 6 |
awarded | Popular Question |
|
May 28 |
awarded | Supporter |
|
May 28 |
awarded | Scholar |
|
May 28 |
accepted | Restore database excluding FILESTREAM data |
|
May 24 |
comment |
Restore database excluding FILESTREAM data You're absolutely right, 12 gig isn't really that much. It was more of a nice-to-have feature than a need-to-have. But if it is as you say, that what I want to do isn't possible, you can post that as an answer so I can accept it. No need to spend any more time on the issue :-) |
|
May 24 |
comment |
Restore database excluding FILESTREAM data @MarkStorey-Smith: the database is mainly accessed using regular queries, through NHibernate (both from an ASP.NET web application and a Windows forms application). How is that relevant? |
|
May 24 |
revised |
Restore database excluding FILESTREAM data edited title |
|
May 24 |
comment |
Restore database excluding FILESTREAM data @jgardner04: that doesn't seem to work. The database ends up in an inconsistent state if I first do a full restore, followed by a restore of the backup containing only the Primary file group (Error message: "The database cannot be recovered because the log was not restored (...) the database could not be brought online because one or more RESTORE steps are needed"). |
|
May 23 |
awarded | Editor |
|
May 23 |
revised |
Restore database excluding FILESTREAM data added 61 characters in body |
|
May 23 |
awarded | Student |
|
May 23 |
asked | Restore database excluding FILESTREAM data |
|
May 23 |
awarded | Autobiographer |
