This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I'm using the lsmigrate command line tool as follows: "C:\Program Files (x86)\Mindscape\LightSpeed\Migrations\lsmigrate.exe" /p:SqlServer2005 /c:"(connection string)" /v:20120727032554 (I have omitted connection string on purpose) The latest migration version of the db is 20120917013636, but after the migration, instead of being 20120727032554, the db version in the database is now 1 less - i.e. 20120917013635 - which seems odd? Am I doing anything wrong that you can see? I'm using SQL Server 2012 locally, but the same thing seems to happen on our staging server running 2008. I have .net Framework 4.5 installed, and am using the latest nightly build of Lightspeed 4 as of 19 September. |
|
|
|
|
No nothing is wrong with what you are doing as far as I can tell and I assume the changes actually applied correctly? The timestamp currently gets set to 1 second prior to the last rolled back version during downward migrations. Let me know if it hasnt actually applied the downward migrations properly though :)
|
|
|
|
