Migrating a db from SSE 2005 December CTP to SSE 2005 Release Version

I have a developer who built an application using the SSE 2005 December CTP and I would like to bring the db's into the official SSE 2005 released version. I have attempted the following:

1. Create the db's in the released version, detach and re-attach the CTP db's. I got an error telling me they were incompatible.

2. Installed CTP version on one server, backed up the db's and then attempted to restore the db's on another server running the official released version of SSE 2005. Got an error attempting that too.

3. Installed the Management Studio for SS 2005 Developer edition thinking that I could connect to the two seperate instances of each server and like I could in EM 2000 run the transfer wizard to move the db's and data from one server to the next. Problem with this is that I can't get an object browser connection established. I have TCP/IP all config'd correctly, too.

Any other ideas where I can go with this at this time?

Thanks in advance.

Bill

Often the easiest way to move databases is to do a Backup and Restore.|||

As you can see from # 2 of my attempts at this, that didn't work. Actual error was:

Database 'xyz' cannot be upgraded because its non-release version (590) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database. (.Net SqlClient Data Provider)

|||

December CTP of what year? 590 is a pre-RTM version of SQL Server from well over a year ago. There is no way to upgrade this database to the current SP2 version, in fact I don't believe you could even open this database in RTM. The only way to move this database would be to go back to the version where it was created, script the database out to T-SQL and run the scripts on a released version of SQL Server.

Mike

sql

Migrating a db from SSE 2005 December CTP to SSE 2005 Release Version

I have a developer who built an application using the SSE 2005 December CTP and I would like to bring the db's into the official SSE 2005 released version. I have attempted the following:

1. Create the db's in the released version, detach and re-attach the CTP db's. I got an error telling me they were incompatible.

2. Installed CTP version on one server, backed up the db's and then attempted to restore the db's on another server running the official released version of SSE 2005. Got an error attempting that too.

3. Installed the Management Studio for SS 2005 Developer edition thinking that I could connect to the two seperate instances of each server and like I could in EM 2000 run the transfer wizard to move the db's and data from one server to the next. Problem with this is that I can't get an object browser connection established. I have TCP/IP all config'd correctly, too.

Any other ideas where I can go with this at this time?

Thanks in advance.

Bill

Often the easiest way to move databases is to do a Backup and Restore.|||

As you can see from # 2 of my attempts at this, that didn't work. Actual error was:

Database 'xyz' cannot be upgraded because its non-release version (590) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database. (.Net SqlClient Data Provider)

|||

December CTP of what year? 590 is a pre-RTM version of SQL Server from well over a year ago. There is no way to upgrade this database to the current SP2 version, in fact I don't believe you could even open this database in RTM. The only way to move this database would be to go back to the version where it was created, script the database out to T-SQL and run the scripts on a released version of SQL Server.

Mike

Microsoft.Jet.OLEDB.4.0 has not been registered. ?

Hi folks,
We've got SQL2005 April CTP i64 running on Win2003 with SP1 appied (Itenium Proc). Last week, one of developer sent me an email with error msg,

: Msg 7403, Level 16, State 1, Line 1

The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.

I ran Component Checker against that box and it found that MDAC2.8 with SP2 installed. I also found from MS site that Jet 4.0 SP8 i64 version available but the installation aborted due to newer version installed on the box. I am stucked. Any advice would be appreciated.

Sunny

Sunny,

It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.

I hope this information proves helpful.

David Sceppa
ADO.NET Program Manager
Microsoft|||

Does MS have some kind of plans for x64 based 64-bit .net apps to connect to Access 2007 or this a permanent solution?

|||

David Sceppa - Microsoft wrote:

Sunny,

It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.

I hope this information proves helpful.

David Sceppa
ADO.NET Program Manager
Microsoft

Would this also be revelant for OPENROWSET queries that use the driver? For example, the following select runs fine on my dev box (32bit SQL 2005), yet fails on our live box ((SQL 2005 64 bit)) .(it is part of a greater process that *should* bein in SSIS, but is being pushed in as a 'quick fix')

select [User Name],[Password], [Store Number] ,getdate(),''2008-12-31 00:00:00.000'',''1980-01-01 00:00:00.000''

from OPENROWSET(''Microsoft.Jet.OLEDB.4.0'',''Excel 8.0;Database=c:\Username and passwords v1.1.xls'',''SELECT * FROM [staff login details$]'')

version info from live:

7 FileDescription SQL Server Windows NT - 64 Bit
8 FileVersion 2005.090.2153.00

Microsoft.Jet.OLEDB.4.0 has not been registered. ?

Hi folks,
We've got SQL2005 April CTP i64 running on Win2003 with SP1 appied (Itenium Proc). Last week, one of developer sent me an email with error msg,

: Msg 7403, Level 16, State 1, Line 1

The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.

I ran Component Checker against that box and it found that MDAC2.8 with SP2 installed. I also found from MS site that Jet 4.0 SP8 i64 version available but the installation aborted due to newer version installed on the box. I am stucked. Any advice would be appreciated.

Sunny

Sunny,

It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.

I hope this information proves helpful.

David Sceppa
ADO.NET Program Manager
Microsoft|||

Does MS have some kind of plans for x64 based 64-bit .net apps to connect to Access 2007 or this a permanent solution?

|||

David Sceppa - Microsoft wrote:

Sunny,

It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.

I hope this information proves helpful.

David Sceppa
ADO.NET Program Manager
Microsoft

Would this also be revelant for OPENROWSET queries that use the driver? For example, the following select runs fine on my dev box (32bit SQL 2005), yet fails on our live box ((SQL 2005 64 bit)) .(it is part of a greater process that *should* bein in SSIS, but is being pushed in as a 'quick fix')

select [User Name],[Password], [Store Number] ,getdate(),''2008-12-31 00:00:00.000'',''1980-01-01 00:00:00.000''

from OPENROWSET(''Microsoft.Jet.OLEDB.4.0'',''Excel 8.0;Database=c:\Username and passwords v1.1.xls'',''SELECT * FROM [staff login details$]'')

version info from live:

7 FileDescription SQL Server Windows NT - 64 Bit
8 FileVersion 2005.090.2153.00

Microsoft.Jet.OLEDB.4.0 has not been registered. ?

Hi folks,
We've got SQL2005 April CTP i64 running on Win2003 with SP1 appied (Itenium Proc). Last week, one of developer sent me an email with error msg,

: Msg 7403, Level 16, State 1, Line 1

The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.

I ran Component Checker against that box and it found that MDAC2.8 with SP2 installed. I also found from MS site that Jet 4.0 SP8 i64 version available but the installation aborted due to newer version installed on the box. I am stucked. Any advice would be appreciated.

Sunny

Sunny,

It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.

I hope this information proves helpful.

David Sceppa
ADO.NET Program Manager
Microsoft|||

Does MS have some kind of plans for x64 based 64-bit .net apps to connect to Access 2007 or this a permanent solution?

|||

David Sceppa - Microsoft wrote:

Sunny,

It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.

I hope this information proves helpful.

David Sceppa
ADO.NET Program Manager
Microsoft

Would this also be revelant for OPENROWSET queries that use the driver? For example, the following select runs fine on my dev box (32bit SQL 2005), yet fails on our live box ((SQL 2005 64 bit)) .(it is part of a greater process that *should* bein in SSIS, but is being pushed in as a 'quick fix')

select [User Name],[Password], [Store Number] ,getdate(),''2008-12-31 00:00:00.000'',''1980-01-01 00:00:00.000''

from OPENROWSET(''Microsoft.Jet.OLEDB.4.0'',''Excel 8.0;Database=c:\Username and passwords v1.1.xls'',''SELECT * FROM [staff login details$]'')

version info from live:

7 FileDescription SQL Server Windows NT - 64 Bit
8 FileVersion 2005.090.2153.00