|
|
Browse by Tags
All Tags » Support (RSS)
Showing page 1 of 2 (15 total posts)
-
We track changes at a table level. Meaning, when a change occurs we write the name of the modified table to a table called df_ChangeTracking. This table is cleared when you call the RefreshTheDatabase method.
-
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.
-
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.
-
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?
-
Sorry, xp_cmdshell is required in the current version of dataFresh. We will investigate alternative options in the future.
-
Hi Bert -
Thanks for the question. If you make a call to the RemoveDataFreshFromDatabase method, it will remove all traces of dataFresh. You can execute dataFresh commands with a different account than your unit tests. Simply supply a different connection string. dataFresh DOES REQUIRE sysadmin rights.
Thanks,
Mike
-
Hi,
I use DataFresh on my Unittests and it's really great but there are a few things that bother me:
- after all the testruns there is always a table df_ChangeTracking left, is there a way to make sure that dataFresh also drops this table after all the unittests so that everything is exactly the same as before the unittests, just a database ...
-
Thank you for the feedback, we have setup a Vista / VS 2005 environment and are attempting to reproduce this issue.
-
Mind posting the code where you are preparing your database?
PREPARE should be called once your database has been created including the execution of setup.sql. If you are calling PREPARE with an argument of false, this will delay the generation of your snapshot, you must then call the CreateSnapshot method. Otherwise your ...
-
I've not come across this issue. Maybe becuase I've not used it that environment. :) I will do a little research, stay tuned.
1
|
|
|