EntropyZero Blogging Server

I just found dataFresh and I'm experimenting with it to see how it could fit into our testing environment.  I’m having some trouble creating the snapshot.  The CreateSnapshot method runs w/o throwing an exception but takes close to 4 minutes on just 20 tables and then on the call to RefreshTheDatabase I get the following error…

 

System.Data.SqlClient.SqlException : Could not bulk insert. File 'C:\Program Files\Microsoft SQL Server\MSSQL\data\Snapshot_SampleDB\User.df' does not exist.

User

Checking identity information: current identity value '1', current column value '0'.

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

 

When I check the directory C:\Program Files\Microsoft SQL Server\MSSQL\data\ on the database server it has the Snapshot_SampleDB directory but the directory is empty.

 

The database is running on a different system than NUnit but on the same network segment, in case that matters.

Is this SQL 2000 / VS2003? Are you calling dataFresh from the API or by using the console application?  Can you send me the create script of your database?

No, send it to me. :) -- mike<dot>brockey<at>ent0<dot>com

---

Mike Brockey
Senior Architect/Owner
EntropyZero Consulting, LLC

was there a resolution for this? i am having the same problem but no folders or files are being created. the snapshotpath has been set to a network share so the client machien were the tests are running and the server can both access it.

question:

    does the snapshotpath have to be visible to both the client and the database server? 

 

Some background. Datafresh works fine while writing unit tests against a test database on the local machine. It is when i attemp to run unit tests against my database server that i get the same error as above. I tried to change the snapshotpath to a UNC (eg. '//server/data') but this did not work.

 

The snapshot path needs to be a path only visible to SQL Server. I've never used UNC for dataFresh but imagine that it should work fine. You would simply need to ensure that the user account that the SQL Server service is running as has access to the network path.

---

Mike Brockey
Senior Architect/Owner
EntropyZero Consulting, LLC

I too am having the same error.  I have narrowed the problem to the database.  I can create a new database which works fine.  However our existing test databases are having the problem. 

Anonymous:

I too am having the same error.  I have narrowed the problem to the database.  I can create a new database which works fine.  However our existing test databases are having the problem. 

 Also, there is no exception or error raised from the failure to create the snapshot.  Only when you call RefreshTheDatabase do you get the error message specified on the first post of this thread.  Furthermore, the refresh will wipe out changed tables!!!

Since I have tried several databases which some work and others don't I suspect a database version incompatability with datafresh.  All tests have been don on my local SQL Server 8 box but some db's have been upgraded from older servers.  Wish I had the source to datafresh and/or could figure this out.

 Thanks.

- Chris chammons@masyscorp.com

952.201.7096

Anonymous:

I too am having the same error.  I have narrowed the problem to the database.  I can create a new database which works fine.  However our existing test databases are having the problem. 

 Also, there is no exception or error raised from the failure to create the snapshot.  Only when you call RefreshTheDatabase do you get the error message specified on the first post of this thread.  Furthermore, the refresh will wipe out changed tables!!!

Since I have tried several databases which some work and others don't I suspect a database version incompatability with datafresh.  All tests have been don on my local SQL Server 8 box but some db's have been upgraded from older servers.  Wish I had the source to datafresh and/or could figure this out.

 Thanks.

- Chris chammons@masyscorp.com

952.201.7096

Two things to check. If you are running SQL 2005 please make sure that you turn on xp_cmdshell.  Also, if you have renamed your computer at any point since installing SQL server, please read and follow the instructions in this post to correct the internal server name that SQL server uses.

---

Mike Brockey
Senior Architect/Owner
EntropyZero Consulting, LLC

It also might be how the stored procedure df_TableDataExtract is being written. Currently the SP won't work if the database  name has a - in it or other special characters,  a  fix could be to encapsulated the db_name() in square brackets  in the source code and for good practice encapsulate the .dbo in square brackets as well