Hello
if we generate a database file on a particular version of ms sql express and in time to come if there are a few more versions of ms sql express out there with the users - if we continue to package with our app a database file from an older version of sql express will that be a problem with users running a newer version of sql express ?
Also what about the converse scenario - where we ship a database file from a newer version of sql while the customer is still running on an older version.
Thanks,
Avinash
Hi,
normally you speak out only the support where you are sure that it works. It you are a userfriendly vendorf :-) you would check the database version and give a message box that the software can′t be installed or will be installed at their own risks because this version isn′t supported by you. Othwise, if you have a fire-and-forget attitude (like some software vendors) you only write the prerequisites on your box or readme.txt stating that the users *should* read that carefully or otherwise won′t get any support.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||Many thanks for your response.
What I wanted to actually know is; since being able to do an auto attach on a database file and because applications in general and smart clients in particular have the ability to bring with them their own database file; surely in time to come there may be several versions of sql express out there with the users.
From your earlier email, I undertand that you are suggesting we perform some kind of a defensive check before we use the database file
But I was curious to hear of any features - upgrade/migration features that express has within it. For example there should be no problem opening a word 97 document in word 2000 but the otherway round may not be possible. But it may not be fully dysfunctional aswell. For example - may be the limitation is that (hypothetically) x, y and z features may not be rendered/rendered corectly. But the document itself should be rendered minus support for the newer features.
Although it may quite a while before the next version of express comes along, I wanted to get an understanding of what potential situations we will need to prepare for with our customers and also what measures we can take now to hopefully ease support to our customers later.
I'm not sure if I've been able to explain what I was unsure about or require clarifications on. Pl let me know if I need to clarify any of my questions.
Thanks and Regards,
Avinash
PS: It will be great if you can point me to some documentation that talks about the issues that I'm not certain about.
|||Hi,
don′t get me wrong, in th most cases you are sure right. There is an automatical upgrade path with attaching databases, even if their service pack level differs, but I wouldn′t rely on that. Although this is a nice cool feature, we would have to go the like the one I mentiond above in Germany due to law restrictions / warranty.
As the version of SQL Server Express and 2000 / 7.0 are upgrade compatible , there sure will be an automated way to upgrade the SQL Server Express version among each other. But due to database changes on the main successor version of SQl Server they are not (AFAIK and my experience is) downgrade compatible.
What can you do ? -Testing testing testing prior to sending out your database version. Thats a way to document that you did your best to eliminate errors. What of a customers calls you and tells "Hey, I did upgrade my database from Version 9.0.2043 to your new version and this didn′t work and my database is crashed."
What about you telling then that you don′t know if that particular version is not compatible for upgrading ? So you would have to go the test afterwards, inform all customers to whom you shipped the upgrade product and extinguish the burning house at the customer site.
But on the other side, what about telling the customers that all version were tested for upgrading and had gone though a quality test at your center and this is a customer specific problem ?
I guess the latter one is more relaxing for the vendors, becasue they can proof that they took care to this scenarios.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||Many thanks Jens Suessmeyer. I think I understand what you are saying.
Thanks and Regards,
Avinash
