SQLPackage.exe - Support on Server 2003

Question

Hi,

We are trying to make our SQL 2012 RC0 database deployment backward compatible with SQL 2008. SQLpackage.exe runs fine on an environment that has SQL 2008 and Windows Server 2008 after we install the required RC0 dll components.

However if the OS is Server 2003, we get this error on even running a script action with SQLPackage.exe:

Unhandled Exception: System.TypeInitializationException: The type initializer for 'Microsoft.Data.Tools.Schema.CommandLine.Program' threw an exception. ---> System.TypeInitializationException: The type initializer for 'SqlSchemaModelStaticState' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Microsoft.Data.Tools.Schema.Common.Diagnostics.EtwProvider' threw an exception. ---> System.PlatformNotSupportedException: This functionality is only supported in Windows Vista and above.

Is SQLPackage.exe officially not supported on Windows Server 2003?
Could someone confirm/point to a page that details the pre-requisites for SQLPackage.exe deployment?

Answer 1

Hi Shriram,

SSDT tools are supported on the following platforms: Windows 7, Windows Server 2008 R2, Windows Server 2008 Service Pack 2, Windows Vista Service Pack 2

SQLPackage.exe depends on the deployment engine, but also other SQL components which are not supported on Windows Server 2003.

SQLPackage.exe can be run from another machine to target a database running on Windows Server 2003.

Hope this helps.

Thanks,

---

Thanks,
Barclay Hill http://blogs.msdn.com/bahill
Sr. Program Manager, SQL Server Data Tools | Microsoft Corporation
Please mark the responses as the answer if it resolves your question/issue.

Answer 2

Hello Shriram,

Such a shame! We were going to use SSDT in order to implement our database upgrading system, but based on the fact that our potential clients will have XP machines in their businesses we just can't. 

It's a shame because the "dacpac v3.0 + SQLPackage.exe + Deploy action" set is one of the best things I've ever seen in database deployment tools world. Two years from now until the end of XP support by Microsoft are too much clients that we would loose and we can't afford it.

It would be wonderful being able to use SSDT in XP somehow.

Regards.

Anti.

Answer 3

Antioco,

Just to be clear, SQLPackage.exe can run from another machine to deploy to Windows Server 2008 or XP with a remote accessible SQL Database instance.  Do you have many clients running a database server on Windows XP Client?

Thanks,

---

Thanks,
Barclay Hill http://blogs.msdn.com/bahill
Sr. Program Manager, SQL Server Data Tools | Microsoft Corporation
Please mark the responses as the answer if it resolves your question/issue.

Answer 4

Just to be clear, SQLPackage.exe can run from another machine to deploy to Windows Server 2008 or XP with a remote accessible SQL Database instance.  Do you have many clients running a database server on Windows XP Client?

I just want to add my voice to the people saying 'huh?? what??". If I had realized that 2003 and XP were not supported, we probably would have stuck with our home grown DB deployment. Now, we have to look at dumping SqlPackage and going back to our home grown solution.

We don't have many customers running their production on XP but, they do run our Developer Edition on their XP workstations so they can develop and test before pushing to production. And, I'm sure we have plenty of customers using Server 2003. It may seem like 2003 is almost 10 years old but remember, it's replacement was only relased 4 years ago.

It seems strange that you support SQL 2005 but not Server 2003. I'll bet that 95% of the SQL 2005 installations are running on Server 2003.

Please see if this decision can be reconsidered. Especially for Server 2003.

Thanks,

John Vottero

Answer 5

Hi Barclay,

Yes. We have many of them. Perhaps it's a rare situation but, here in Spain, we have seen many many many clients with XP. Our application will run on machines with XP (Vista and 7 of course) because we need a good implantation in the market. Many of our clients will only have a single machine (XP) in their little companies so it won't be possible to deploy from another Vista or W7 machine. 

We are going to use DbMigrations from Entity Framework 4.3.1. It's a little messier to deal with them, but it's a powerful tool too.  

Thanks,

Antíoco

Answer 6

I am caught in a similar situation as well.  I have been using VSDBCMD for the past 2 years to deploy our database schemas within the client application.  This has worked  beautifully, just fine on Windows XP.  Now that VSDBCMD is being dropped (no deployment support for SQL 2012), I have looked into SqlPackage.exe.  The big problem for me is that SqlPackage does not work on Windows XP.

Please fix SqlPackage to run on XP, or fix VSDBCMD to deploy to SQL 2012!!!

Answer 7

BUMP!

We need support for DACPACs to be deployed from XP.

Answer 8

I do not understand, why don't you stay with Visual Studio database projects (VSDBCMD.EXE) if that works, as SQL Server 2012 does not run on Windows XP nor Windows Server 2003 or Windows Server 2003 R2?

---

Milo A. Hoffman

Answer 9

Because I now have to maintain two database projects (vsdb and ssdt) if I am to support deploying to sql2012. I have countless customers still on xp and can not abandon them.

Answer 10

BUMP! We need VSDBCMD to be fixed to deploy to SQL 2012.

Answer 11

VSDBCMD will not be updated to support SQL Server 2012.  SqlPackage.exe is the replacement for VSDBCMD.exe and supports 2005, 2008, 2008 R2, 2012, and Windows Azure SQL Databases.

We have no plans to support Windows XP as SQL Server 2012 does not support XP and XP is no longer in mainstream support. 

You may want to try the September version of DACFX.  While it no blocks longer running on Windows XP/Windows Server 2003 it is still not supported. Link below.

___________________________________________________

Microsoft® SQL Server® 2012 Data-Tier Application Framework (September 2012) The Microsoft® SQL Server® 2012 Data-Tier Application Framework (September 2012) provides application lifecycle services for database development and management.

FREE Release Date: 9/7/2012

---

Thanks,
Barclay Hill http://blogs.msdn.com/bahill
Sr. Program Manager, SQL Server Data Tools | Microsoft Corporation
Please mark the responses as the answer if it resolves your question/issue.

Answer 12

For those that will try Windows XP and SqlPackage.exe in the unsupported mode as described above, it appears Windows XP will not be able to run the operations.  SqlPackage.exe depends on some functionality in NETFX 4 which was not added to Windows XP SP3.  It was added to Windows Server 2003 in SP2. 

---

Thanks,
Barclay Hill http://blogs.msdn.com/bahill
Sr. Program Manager, SQL Server Data Tools | Microsoft Corporation
Please mark the responses as the answer if it resolves your question/issue.

Answer 13

Any idea what that functionality is?  I'm fine working in unsupported mode since I wouldn't have to package VSDB and SSDT projects for deployment.  It would also mean I can move to VS2012.

Answer 14

I will put up a blog post tonight on sqlproj.com on how to make it work. Found a way last night.

---

-GertD @ www.sqlproj.com

Answer 15

You sir are a gentleman and a scholar.

Answer 16

Here you go: http://sqlproj.com/index.php/2012/09/sqlpackage-exe-on-windows-xp/

---

-GertD @ www.sqlproj.com