Easwaran Paramasivam
asked on
'Current database version not in valid format' error while upgrading a database
I've an DB installer which upgrades from older version to new version successfully with local database. But my customer shared a database with older version. While upgrading the database it throws error as 'Current database version not in valid format'. Please do refer the attached screenshot. What could be the cause for the issue? How to resolve it? Please do suggest. Thanks.
DBUpgradeErr.jpg
DBUpgradeErr.jpg
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
@jimpen: Thanks.
Could you please say how to create installer package for a DB? It could be either Fresh DB install or Upgrade existing DB.
Could you please say how to create installer package for a DB? It could be either Fresh DB install or Upgrade existing DB.
I was really only on the deployment/upgrade team not the dev team. So take this with a block of salt.
From what I could tell they used the script DB from the SQL management studio, including the baseline data. That would be for a new DB. Then from the baseline the programmers would have to build the various SQL scripts to add/change an object.
Really it is a matter of getting the dev staff to figure out what are the DB changes and what are app changes and the changes needed on both sides.
I know it sounds like I'm hinting for a job. I'm not. I'm a production DBA and know how to do troubleshooting. If you look in my profile you can find my personal e-mail address. I can forward the info to the developer and you two can figure out costs etc.
From what I could tell they used the script DB from the SQL management studio, including the baseline data. That would be for a new DB. Then from the baseline the programmers would have to build the various SQL scripts to add/change an object.
Really it is a matter of getting the dev staff to figure out what are the DB changes and what are app changes and the changes needed on both sides.
I know it sounds like I'm hinting for a job. I'm not. I'm a production DBA and know how to do troubleshooting. If you look in my profile you can find my personal e-mail address. I can forward the info to the developer and you two can figure out costs etc.
ASKER
Thanks.
Fist things first. Make sure you have a valid backup (valid means test a restore somewhere).
Now run CheckDB on the database, or the database restored version. It should not matter.
For reference:
http://msdn.microsoft.com/en-us/library/ms176064(v=sql.100).aspx
Now report back what CheckDB output is, and well take it from there.
Regards Marten