re: The AdventureWorks 2008 Family of Sample Databases

BAleiHi — Fri, 26 Sep 2008 08:00:59 GMT

I can't get it to install. I'm running XP and SQL Server 2008 Express and want to install the AdventureWorks OLDP x86 version (specifically, SQL2008.AdventureWorks_OLTP_DB_v2008.x86.msi). When I installed SQL Server I forgot to enable FILESTREAM. When I went to install AdventureWorks, I got that error so I went back and, using SQL Server Configuration Manager I enabled FILESTREAM for the only instance that I have on my machine. I should note that I'm logged into XP under a different user than the one that started the service but they both have full admin privs.

So with FILESTREAM enabled, my AdventureWorks install goes seamlessly. Only problem is that there's not database anywhere. The only thing I find is a .BAK version in the 100/Tools/Samples folder. There's a script there to restore and when I run it in SQL Server Management Studio I get the error:

Msg 5591, Level 16, State 4, Line 1

FILESTREAM feature is disabled.

Msg 3013, Level 16, State 1, Line 1

RESTORE DATABASE is terminating abnormally.

Msg 5011, Level 14, State 5, Line 1

User does not have permission to alter database 'AdventureWorks2008', the database does not exist, or the database is not in a state that allows access checks.

Msg 5069, Level 16, State 1, Line 1

ALTER DATABASE statement failed.

What's up with this? TIA

re: The AdventureWorks 2008 Family of Sample Databases

bonniefe — Fri, 26 Sep 2008 19:33:01 GMT

This is a feature of FILESTREAM. There are two components of enabling FILESTREAM. If you enable it during setup then both components are enabled. If you enable it after setup, you need to enable both pieces of FILESTREAM separately. See http://blogs.msdn.com/sqlserverstorageengine/archive/2008/03/03/filestream-configuration-and-setup-changes-in-sql-server-2008-february-ctp.aspx for details about how to enable both aspects of FILESTREAM. If you would prefer a simpler approach to enabling FILESTREAM I recommend that you file a SQL Server bug at http://connect.microsoft.com/.