PostgreSQL 8.0 to Microsoft SQL Server 2008 migration - sql-server

I am migrating a large (500 GB) database containing several hundred tables and a few database functions from PostgreSQL 8.0 to Microsoft SQL Server 2008.
Is there a website (or book) that details differences I need to be aware of (data types, stored procedure functionality, etc.)?
I am fairly familiar with PostgreSQL, but just learning SQL Server.
Any SQL Server book recommendations would also be appreciated.
Thanks.

Take a look at these links:
Microsoft SQL Server to PostgreSQL Migration by Ian Harding
This is going the other way, but has some of the information you need.
Cross compare of SQL SERVER 2005, MYSQL, and PostgreSQL 8.3

Related

Converting database from SQL-Server 2008 to SQL-Anywhere

Please tell me about the main advantages of SAP SQL-Anywhere and the main differences it has with SQL-server 2008. While installing SQL-server 2008 in various computer systems, the installation does not happen smoothly at times, so we try to solve this problem by using SAP SQL-Anywhere.
Is it possible to convert a SQL-server 2008 database in to a SAP SQL-Anywhere database?

Proper way to Import data from Access to SQL Server?

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

developing SQL 2005 application using SQL 2008 server

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.

copying oracle to sqlserver 2005 jdbc

Is there any way of copying a database from oracle to sqlserver 2005? Thanks
You can migrate from Oracle to SQL Server with Microsoft's SQL Server Migration Assistant. It is available both to SQL Server 2005 and 2008.
If you have lots of (complicated) stored procedures and such, the migration might get a bit tedious. I have only experience with databases with simple procedures and could just rewrite them and do the data copy to empty tables in SQL Server with the import functionality using Oracle connector (usable from SQL Server if you have installed Oracle client tools to the SQL Server machine). This way I didn't even need to use the Migration Assistant tool.

SQL Server to Oracle10g conversion

I currently have a SQL Server (Express 2005) database to hold some transaction/metadata that I now want to migrate to Oracle 10g express instance.
Can you do this programmatically or is there a decent software tool that anyone can recommend?
Oracle Migration Workbench is included in SQL Developer. Check it out to see if it meets your needs.

Resources