June 4, 2009 at 4:41 am
I need to migrate one MS SQL Srever 2000 Server to MS SQL Server 2008. The applicaton is using VB 6.0 and ADO. I want to confirm is there any compatibility issue will occur at application level if I do the migration.
June 4, 2009 at 10:01 am
The ADO interfaces should be backwards compatible, but you need to test. You cannot do this migration without testing your specific application against a 2008 server.
June 5, 2009 at 2:14 am
I don't know if there is any difference between SQL Servwer 2005 and 2008 but
there is no problem running 2005 with VB6 ADO and ODBC (SQL Server). I do this on a Win 2003 server 64 bit.
I for some years ago migrated from SQL server 2000 to 2005 without changing one line code in VB6. But test your application!
Now I have migrated to VB.net and ADO.net to get much better performance (64 bit). This works really nice.
I will also upgrade to 2008 but there is no rush today to do it.
/Gosta
June 8, 2009 at 3:13 am
Steve is right. There is nothing in the products that will prevent this from working but you do need to test.
The most likely problems will be in your application, as some T-SQL syntax that worked on older versions of SQL Server is not supported in SQL Server 2008. Hopefully your application will fail if any of this happens rather than ignoring the problem, but you can never be sure what people have coded...
If you are not sure what you need to test, then you should ask Google to tell you about 'Regression Testing'. The purpose of this is to prove thet your application gives the same results in the new environment as it did in the old.
You take a backup of your database and restore it to a SQL 2000 server and run a series of tests with your application and take note of all the results.
You take the same backup and restore it to SQL Server 2008 and run the same tests in the same order. The results should be the same. If they are different you need to investigate why.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
September 29, 2010 at 10:17 am
I'm having a migration headache with this.
I have connected to MSSQL 2008 using MDAC (ADO) 2.6 no problem.
However when using MSSQL 2008 AAS (OLAP Analysis server) I can't connect, even after I upgraded to ADOMD 2.8.
This worked OK in MSSQL 2000 & 2005 Analysis server
The error I get is...
Unable to connect to the Analysis server. The server name 'PC112\SQL2008' was not found. Please verify that the name you entered is correct, and then try again.
I don't really want to have to rewrite my OLD VB6 apps in VB.net with ADOMD.net, but right now I can't see any alternative.
Has anyone come across this problem ?
November 12, 2010 at 10:17 am
http://msdn.microsoft.com/en-us/library/bb264566(SQL.90).aspx
USE THIS!!!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply