I knew that there was a toolkit to help move an application from Oracle to SQL Server, but I hadn’t appreciated that there was one for Sybase and Access these also now come in two flavours, one to move you to SQL Server 2005, and one for SQL Server 2008:
SQL Server 2005 Migration Assistant for:
SQL Server 2008 Migration Assistant for:
Before you ask, there aren’t any assistants fromMicrosoft to do migrations to these platforms from SQL Server, although I am sure that Oracle and Sybase will be happy to help with that. What I can’t understand is why anyone would go this way, so post some comments and enlighten me.
I'm in the middle of a migration from Sybase ASE on Solaris to SQL Server 2008. Have worked through most issues so far but one. In Sybase ASE you have an identity_gap parameter that defines the sze of the block of ID numbers in the table's object allocation map. This has to do with the db server "caching" a list if id numbers for use with an identity column and you ending up with a mess if the server goes down without the proper shutdown. Is there an equivlent in SQL Server or does SQL Server just grab the next ID number one at a time?
I am not aware of any caching we just grab the next one afaik