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.
Related
I am new here. I was recently handed a project to create an environment with Windows 2012 and SQL Server 2012. The goal is to take the existing databases in our current environment which is SQL Server 2005 and Windows 2003 platform. I have tried looking for specific whitepapers to doing this or checklists that might exist. What are some of the things I should plan for, can I de-attach a database in the SQL Server 2005 environment. I did check the compatibility version for SQL Server 2005 environment is 90. Any help would be appreciated. I feel as if I might be in over my head.
I don't recommend the De-attach/attach method. De-attach/attach method will only work with the database but you will have to manually create the jobs. There will be other issues.
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).
Very new to SQL Server. I am needing to develop a SQL Server database to run with an iPhone app I am developing. It will ultimately be running with our full-fledged SQL Server database, which is administered by our IT guy, but I'd like to have a local database for testing.
Two questions:
I assume I can use SQL Server Express 2012 for this purpose, since it is advertised as such; but would it be better/easier to use what appears to be the simplest form, LocalDB, in conjunction with VB2010? It will be running on my office PC to which a port is open for TCP communication from my app (which is working fine). Would LocalDB work for that, if the communication occurs in the VB app? Or will I need to get the SQL Server Express edition?
If a prototype database is developed in SQL Server Express, can it migrate to our full-fledged SQL Server when the app is taken "live"? (I am not sure right now what version our full-fledged SQL Server is, but I was planning on using SQL Server Express 2012.)
Yes, the Express editions ARE the full-fledged SQL Server version - no code difference, only some marketing-driven restrictions (on database size and so forth).
You can absolutely develop your system on a SQL Server Express, and then just detach your database from Express and re-attach it to a Standard or Enterprise edition server. No fuss, no migration, no conversion - nothing - it just works. Period.
And I would probably even argue having a server installation (of your Express) edition is the better choice than LocalDB. That way, you're already using the server-based approach as you will later on in production, and you won't fall into any "convenience" traps offered by LocalDB (or other approaches) that make dev life easier - but rollout to production can be a challenge. When you use SQL Server Express as a server-based installation from the get to - you have the "real deal" from day one.
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.
What I have found on the 'net seems a little ambiguous whether or not something needs to be installed on the server to use the Sync Framework with SQL Server 2005.
My interpretation is no, that the ADO.NET'ness of the product reaches out to the server (assuming appropriately trackable tables exist).
My goal is to use SQL Compact on the client and Sync with SQL Server 2005 with no install on the server.
A little help would be great!
Thanks,
rusty
Other than the change tracking infrastructure (SQL Server 2008 Change Tracking or Triggers etc), you will not need to install any Sync Framework components on the SQL Server machine to be able to include it in a Sync topology.
Cheers,
Scott
As far as I know, SQL Server 2005 does not need the Microsoft Sync Framework installed.