I am developing an application for one of my customer who has SQL 2005 but I have SQL 2008 on my system. Can I develop my application using SQL 2008 and then ported it simply to SQL 2005? I will use EF and C# for my application and the SQL DB has database (no code).
Just install SQL Server 2005 express and use that
At some point, developing an backward compatible app will come back to bite you because there are differences in data types, deprecated features, discontinued features, and behaviour changes. The list is too long to try and remember for development
Short answer: yes.
But there are some differences between SQL 2005 and SQL 2008 databases. You should read up on those to make sure your database is compatible with SQL Server 2005.
For example some datatypes only exists in the one version and not the other and so on.
Related
We have several SQL Server databases at work and we plan to keep all of them in a Database Server. However, while we use SQL Server 2014 in some of the databases, there is also a database (let's say ABC) with the version of SQL Server 2008 R2.
The problem is that; ABC is a database originated from another company and sometimes it is updated by them using scripts, etc. So, this means that we have to go together with the version they use. As far as I know, it is possible to restore a database of version 2008 R2 in the version of 2014 but the reverse operation is not possible (to restore a database of version 2014 in the version of 2008 R2).
So, in that case what is the best way to solve this problem by using the single database (SQL Server 2014) on the same server?
You can generate database from the 2014, 2008 compatible. You can dig into the advanced option and you will find creating scripts for triggers, indexes and all dependent objects.
Generate Scripts
Choose Compatibility
Specify Data generating scripts
The server could be 2014.
You just need get SQL Server Management Studio (SSMS) version 2008 and generate backup using it.
You could have lots of SSMS versions.
We are looking to replace SQL SERVER replication.
Today we've got several version on SQL installations because SQL replication does not support working with different SQL versions (2005 and 2008 for example), so instead of having several installation of SQL version (2005,2008,2012 etc...), we are looking install a single version on the server (let's say 2014) and using this version to replicate between all our clients (2005+).
Today we are using transnational and merge replication at the same time for each database.
I would like to know:
Is there a way to make different version replicate with each other?
Is there and good tool that can replace that replication?
SQL Server 2014 supports replication with SQL Server 2008 and on. https://msdn.microsoft.com/en-US/library/ms143550(v=sql.120).aspx
So if you use SQL Server 2012 as backend, SQL Server 2005, 2008 and 2012 clients are supported.
We are using transnactional replication between 2012 and 2016 and 2014 and 2016. For us the trick was to create a publisher on the older version and a pull subscription on the newer version. The only other thing to watch out for is you need to manage the relationship in SSMS using the older server as trying to go to properties from the 2016 box will throw an error.
I saw something about changing data types or another server setting that would eliminate the errors so it might be worth looking around.
I'm asking for the proper way, in SQL Server's T-SQL (I think that's what it is) code or using another language, to import data from a Microsoft Access MDB Database into a new SQL Server Database.
Now, typically I would just import it in. The problem is I'm writing a .SQL script (I could use another technology if needed) to do all this leg work as this will need to be done fairly regularly. Likely at least once a week, for about 5 months in the year.
To digress a tad, I had wanted to implement a single database and distinguish separate source database using something like a DatabaseID field, but the powers that be overthrew me there.
I was previously using SQL Server Management Studio 2012 with SQL Server 2008 running the T-SQL (on a production machine) that worked fine. I've now migrated to a local SQL Server Management Studio 2012 with SQL Server 2012 (for development) and the code that used to work doesn't anymore.
This code is what used to work: SELECT * INTO [dbo].[Controls] FROM OpenDataSource('Microsoft.Jet.OLEDB.4.0', 'Data Source=C:\Show.mdb; Jet OLEDB:Database Password=BobSaget')...[Control] The password has been obfuscated for security ...
That's likely a sloppy solution. What's the ideal way?
Thanks in advance!
I would recommend using Microsoft's SQL Server Migration Assistant for Access.
SQL Server Migration Assistant (SSMA) is a free supported tool from Microsoft that simplifies database migration process from Access to SQL Server. SSMA for Access automates conversion of Microsoft Access database objects to SQL Server database objects, loads the objects into SQL Server, and then migrates data from Microsoft Access to SQL Server.
SSMA for Access v5.2 is designed to support migration from Microsoft Access 97 and higher to all editions of SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Azure.
You can find it here.
You may need to fix the structure after the migration as it tends to over exaggerate many of the data types.
Have you checked your DCOM security on MSDAINITIALIZE?
I had this problem when moving to a local instance of SSMS 2012.
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2011/09/28/troubleshooting-cannot-create-an-instance-of-ole-db-provider.aspx
Hello everyone i have got a project to migrate from SQLAnywhere 11 to any new relational databases for our ship crew web application.The reasons for migrating is cost and support issues.I will need to choose a database which is free and has all features as SQLAnywhere 11.0.
Here is the list of Questions i want to know about SQL Server 2008 R2 express.
Do we have any migration utility to move from SQL Anywhere 11 to SQL Server 2008 R2 express.
How easy is deployment of SQL Server 2008 R2 express from install shield MSI.
Alternative methods to migrate from SQLAnyhere 11 to SQL server 2008 R2 express.
Do management tools come free with express addition. I should be able to defragment and restore the database.
Thank you
There is a SQL Server Migration Assistant (SSMA) for Sybase (v 5.1 was released just this week), but I am not familiar enough with SQL Anywhere to assure you whether, or how well, it works:
http://blogs.msdn.com/b/ssma/archive/2011/07/12/announcing-sql-server-migration-assistant-ssma-v-5-1.aspx
Deployment of SQL Server Express is relatively easy, but I haven't done any work recently incorporating this into a more complex installer.
If you use Express w/Tools or Express w/Advanced Services, they come with Management Studio Express. You can also download this separately:
http://www.microsoft.com/download/en/details.aspx?id=22985
Note that Management Studio Express is missing some of the SSMS functionality, such as managing agent, so if you have to manage other editions you may be better off investing $49 (or less, depending on vendor) into the developer edition, which comes with the full version of SSMS.
We have a production web and database server with SQL Server 2000. (However, a few clients they have their own servers with SQL 2005.) So we have local installs of SQL 2005 Express for development on Windows XP SP3 boxes (which don't allow SQL 2000 Enterprise installations).
We often need to copy SQL 2000 databases to SQL 2005 instances. In the past, we have used the SQL Publishing tool (also mentioned here). However, one of our databases is so big that using that tool fails as it creates SQL scripts that get too large for Management Studio to handle them properly. Besides, it takes too long... :)
We would use the Copy Database Wizard included with SQL 2005, but our development machines run SQL 2005 Express which don't included SQL Server Agent, which is required for Copy Database Wizard to work. So, I guess our solution will be to upgrade our development installs with the full version of SQL 2005 (we have an MSDN subscription of course).
I was wondering what other solutions, if any, work well for you guys? (Besides complaining to the bosses to upgrade our production servers to 2005 or even 2008--which I've already tried.)
Back it up in SQL Server 2000 and then use the RESTORE WITH MOVE command into 2005 Express.