I am developing a Web Application using SQL Server 2005 for the database, but will need to deploy the database to SQL Server 2000 in the production environment.
We don't have a license for SQL Server 2000 (we've only got for 2005), and I've come accross a range of incompatibilites and issues when migrating the DB from 2005 to 2000.
I was hoping I could switch my development DB over to MSDE 2000, and then depoy it to SQL Server 2000 when in production.
Will this work? Is MSDE compatible with SQL Server 2000? How easy is it to migrate from one to the other? Is it as simple as a backup and restore?
Yes.
And it is as simple as a backup and restore.
Caveat: be sure both server and dev machine are running the same service pack. IIRC, that could matter.
MSDE does have some feature limitations, but as long as you aren't using features only supported on the full server version, you should be fine.
Related
Since we need to move around our database a lot (like update it with new Rows which are generated by code and then update it prod db and reverse process). SQL Server CE, being a file based system was very helpful.
We would like to upgrade to use SQL Server Local Db but at the same time, it has limitations of use with IIS (though possible with AttacheDbFile). In this regard, since LocalDb is more or less a version of SQL Server Express, would it be possible to use our SQL Server LocalDB .mdf in our development environment and then copy them in prod but use by attaching to a SQL Server Express instance?
If yes, what additional thing, we need to do make it possible?
Also, we would like the reverse process to be worked out as well, mean detach the .mdf file and use it as LocalDb in development environment. I have read the great blog articles of
Krzysztof Kozielczyk also but not have experimented much with LocalDb.
LocalDB IS SQL Server Express (introduced with SQL Server 2012 Express), and the .mdf file is identical between LocalDB and SQL Server Express (and even a "full" SQL Server edition like Web, Standard or Enterprise Edition).
The only caveat is: you need to be using the same versions of those databases, since the file format is only identical amongst same versions, and can only be used amongst the same versions (e.g. 2012) - or it can be "upgraded" to the next newer version (e.g. you could move a database from LocalDB 2012 to a SQL Server 2014 Express once it's released) - but you can never go back down to an earlier version (you cannot take a LocalDB 2012 .mdf database file and attach it to a SQL Server 2008 version).
I have this question about the SQL Server and SQL Server Express.
In my client machine, the database that he's using is SQL Server 2012 and in my machine i have SQL Server 2005.. so i want to install another instance and a friend told me that i dont need to install the SQL Server 2012 Standard (the one that they have) and with the SQL Server 2012 Express will work.. is that ok?
I really don't know the real difference in working with SQL Server Express 2012 and SQL Server Standard 2012 (with the same database).
On of the major differences is that with express you not be able to back ups over the network. Local backups only. When I do back ups from the SqlExpress Server Manager Studio it doesn't recognize mounted drives. Check out this for a more formal approach to your question
[http://msdn.microsoft.com/en-us/library/cc645993.aspx][1]
Check through this document:
Features supported by the editions of SQL Server 2012
You will soon be able to see if there are any features that you are using in standard that are not available in express.
I was wondering if we could backup the database that we currently host on regular SQL Server, and put it onto our clients computer when we setup SQL Server Express for them.
Is this possible?
Thanks,
Matt
Yes, it's possible to restore a database backup from the Standard edition to the Express edition. It's not possible to restore a SQL Server 2008 to a SQL Server 2005 version, though.
However, there a some minor differences between versions. I've noticed an issue in SQL Server Express 2005 when calling .NET SQL CLR functions across databases, so your mileage may vary. I haven't been able to find a good overview of the exact differences between the various SQL Server editions.
It's always best to keep the development platform as close as possible to the release platform. I can only recommend that you use the Express edition of SQL Server for development as well; and re-test your application.
There is a project that a developer is suggesting to use MSDE instead of SQL Server, I need to know the differences and limitations of MSDE to make sure it will be able to handle our project.
If I remember well MSDE ( Microsoft Desktop Engine or something like that ) is the precursor of SQL Server 2005, 2008 Express Editions. MSDE does not come with a management tool like SQL Server 2008 R2 Express, for example. Also MSDE comes with some constraints that in 2011 are antique ( 1GB for database or 1GB RAM for the server that hosts the MSDE).
In conclusion , my advice is go with the latest SQL Server Express Edition.
a) I am in the process of developing a web site using the new free web development tool - Webmatrix (Beta 2) from Microsoft.
b) Web Platform Installer (recommends and also) automatically installs SQL Server Express 2008 along with Webmatrix and VWDE 2010 Express.
c) My database is created in SQL Server Express 2008. But the hosting company says that they would support only SQL Server Express 2005 (but not SQL Server Express 2008).
d) Can I go ahead with this hosting company or should I look for somebody who supports SQL Server Express 2008 specifically? In other words, the crux of the issue is:
Is it possible to open, read, update the database and tables created using SQL Server Express 2008 in SQL Server Express 2005 edition also?
Esh
I had the similar issue with hosting company.
They gave me a bak file from SQL server 2008 and I tried to restored in in my SQL 2005 environment and it consistently failed. Quite surprised to see the lack of backward compatibility. I would advise to go with hosting provider who supports 2008 or you migrate your DB to 2005.
In one word: NO.
SQL Server is never backwards compatible - if you have a database in a 2008 version, there is no way to restore and use that on a SQL Server 2005 machine. There's no trick, no third-party tool, no hack, nothing - it just doesn't work. EVER.
So if your hoster supports only SQL Server 2005 Express, you need to uninstall 2008 Express and manually install 2005 Express on your dev machine.
Or find a hoster that support SQL Server 2008 Express.