ExportSqlCE Wiki & Documentation Rss Feed

Updated Wiki: Command line utilities

ErikEJ — Thu, 10 Jan 2013 08:16:02 GMT

This project contains 4 command line applications:

- ExportSqlCE - for scripting an entire SQL Server Compact 3.5 database
- ExportSqlCE40 - for scripting an entire SQL Server Compact 3.1 database
- ExportSqlCE31 - for scripting an entire SQL Server Compact 3.1 database
and
- Export2SqlCE - for scripting an entire SQL Server 2005/2008 database providing SQL Compact compatible T-SQL statements.

Command line for ExportSqlCE, ExportSqlCE40 and ExportSqlCE31:

C:\Data\SQLCE\bin>exportsqlce
Usage :
  ExportSQLCE.exe [SQL Compact Connection String] [output file location] [exclude] [schemaonly|dataonly] [saveimages] [sqlazure]
Examples:
  ExportSQLCE.exe "Data Source=D:\Northwind.sdf;" Northwind.sql
  ExportSQLCE.exe "Data Source=D:\Northwind.sdf;" Northwind.sql exclude:Shippers,Products

Usage: (To create a schema diff script)
  ExportSQLCE.exe diff [SQL Compact or SQL Server Connection String (source)] [SQL Compact or SQL Server Connection String (target)] [output file location]
Example :
  ExportSQLCE.exe diff "Data Source=D:\Northwind.sdf;" "Data Source=.\SQLEXPRESS,Inital Catalog=Northwind" NorthwindDiff.sql

Usage: (To create a database graph)
  ExportSQLCE.exe dgml [SQL Compact or SQL Server Connection String (source)] [output file location]
Example:
  ExportSQLCE.exe dgml "Data Source=D:\Northwind.sdf;" C:\temp\northwind.dgml

Usage: (To create a Windows Phone DataContext)
  ExportSQLCE.exe wpdc [SQL Compact or SQL Server Connection String (source)] [output file location]
Example :
  ExportSQLCE.exe wpdc "Data Source=D:\Northwind.sdf;" C:\temp\Northwind.cs

Usage : (To script an entire database to SQLite format)
 ExportSQLCE.exe [SQL CE Connection String] [output file location] [sqlite]
Example:
 ExportSQLCE.exe "Data Source=D:\Northwind.sdf;" Northwind.sql sqlite

Command line for Export2SqlCE:

Usage :
 Export2SQLCE.exe [SQL Server Connection String] [output file location] [[exclude]] [[schemaonly]] [[saveimages]] [[preservedateanddatetime2]] [[keepschema]]
 (exclude, schemaonly, saveimages, keepschema and preservedateanddatetime2 are optional parameters)

Examples :
 Export2SQLCE.exe "Data Source=(local);Initial Catalog=Northwind;Integrated Security=True" Northwind.sql
 Export2SQLCE.exe "Data Source=(local);Initial Catalog=Northwind;Integrated Security=True" Northwind.sql schemaonly
 Export2SQLCE.exe "Data Source=(local);Initial Catalog=Northwind;Integrated Security=True" Northwind.sql exclude:dbo.Shippers,dbo.Suppliers

Notice that the SQL Server Export currently does not support identically named tables in different schemas.

Command line utilities optional parameters:

exclude:
- list of tables to be excluded from scripting, separated by commas - sample: exclude:dbo.Shippers,dbo.Products

schemaonly:
- this will cause the script to not contain any data, by only table and constraint definitions - so no INSERT statments in the script.

dataonly:
- this will cause the script to contain INSERT statments only.

saveimages
- this will cause all image field data to be written to individual files rather than be included in the script. The files are named <NewGuid()>.blob, and are in the same folder as the generated script. The resulting script and related files can used by SqlCeCmd to import into a SQL Compact database file. This can be useful if your database contains large image fields (5-10 MB or more), in order to avoid out of memory errors.

sqlazure
- this will cause primary keys to be scripted before any INSERT statements, batch INSERTS in a GO per 1000 statements, and removes support for ROWGUIDCOL (which is not available in SQL Azure)

diff
- this will generate a SQL Schema Diff script based on differences between source and target data sources.

dgml
- this will generate a .dgml file and releated .sqlce/.sql files in the specified folder, that contains a diagram of the data source.

wpdc
- this will generate a .cs or .vb file with a Windows Phone specific Linq to SQL DataContext and related classes. Requires the Windows SDK version 7 to be installed.

sqlite
- this will generate a .sql script in SQLite3 dump file format, for more information see my blog post here

preservedateanddatetime2
- if this switch is not set (the default), Server columns of type "date" and "datetime2" are converted to datetime columns (which could cause data loss). If the switch is set, the columns are converted to nvarchar(10) and nvarchar(27), preventing any data loss.

keepschema
- this will create table names like "dbo.Shippers" instead of just "Shippers"

Updated Wiki: Command line utilities

ErikEJ — Thu, 10 Jan 2013 08:13:47 GMT

C:\Data\SQLCE\bin>exportsqlce
Usage :
  ExportSQLCE.exe [SQL Compact Connection String] [output file location] [exclude] [schemaonly|dataonly] [saveimages] [sqlazure]
Examples:
  ExportSQLCE.exe "Data Source=D:\Northwind.sdf;" Northwind.sql
  ExportSQLCE.exe "Data Source=D:\Northwind.sdf;" Northwind.sql exclude:Shippers,Products

Usage: (To create a schema diff script)
  ExportSQLCE.exe diff [SQL Compact or SQL Server Connection String (source)] [SQL Compact or SQL Server Connection String (target)] [output file location]
Example :
  ExportSQLCE.exe diff "Data Source=D:\Northwind.sdf;" "Data Source=.\SQLEXPRESS,Inital Catalog=Northwind" NorthwindDiff.sql

Usage: (To create a database graph)
  ExportSQLCE.exe dgml [SQL Compact or SQL Server Connection String (source)] [output file location]
Example:
  ExportSQLCE.exe dgml "Data Source=D:\Northwind.sdf;" C:\temp\northwind.dgml

Usage: (To create a Windows Phone DataContext)
  ExportSQLCE.exe wpdc [SQL Compact or SQL Server Connection String (source)] [output file location]
Example :
  ExportSQLCE.exe wpdc "Data Source=D:\Northwind.sdf;" C:\temp\Northwind.cs

Usage : (To script an entire database to SQLite format)
 ExportSQLCE.exe [SQL CE Connection String] [output file location] [sqlite]
Example:
 ExportSQLCE.exe "Data Source=D:\Northwind.sdf;" Northwind.sql sqlite

Command line for Export2SqlCE:

Usage :
 Export2SQLCE.exe [SQL Server Connection String] [output file location] [[exclude]] [[schemaonly]] [[saveimages]] [[preservedateanddatetime2]] [[keepschema]]
 (exclude, schemaonly, saveimages, keepschema and preservedateanddatetime2 are optional parameters)

Examples :
 Export2SQLCE.exe "Data Source=(local);Initial Catalog=Northwind;Integrated Security=True" Northwind.sql
 Export2SQLCE.exe "Data Source=(local);Initial Catalog=Northwind;Integrated Security=True" Northwind.sql schemaonly
 Export2SQLCE.exe "Data Source=(local);Initial Catalog=Northwind;Integrated Security=True" Northwind.sql exclude:dbo.Shippers,dbo.Suppliers

Notice that the SQL Server Export currently does not support identically named tables in different schemas.

Command line utilities optional parameters:

exclude:
- list of tables to be excluded from scripting, separated by commas - sample: exclude:dbo.Shippers,dbo.Products

schemaonly:
- this will cause the script to not contain any data, by only table and constraint definitions - so no INSERT statments in the script.

dataonly:
- this will cause the script to contain INSERT statments only.

saveimages
- this will cause all image field data to be written to individual files rather than be included in the script. The files are named <NewGuid()>.blob, and are in the same folder as the generated script. The resulting script and related files can used by SqlCeCmd to import into a SQL Compact database file. This can be useful if your database contains large image fields (5-10 MB or more), in order to avoid out of memory errors.

sqlazure
- this will cause primary keys to be scripted before any INSERT staements, batch INSERTS in a GO per 1000 statements, and removes support for ROWGUIDCOL (which is not available in SQL Azure)

diff
- this will generate a SQL Diff script based on differences between source and target data sources.

dgml
- this will generate a .dgml file and releated .sqlce/.sql files in the specified folder, that contains a diagram of the data source.

wpdc
- this will generate a .cs or .vb file with a Windows Phone specific Linq to SQL DataContext and related classes. Requires the Windows SDK version 7 to be installed.

sqlite
- this will generate a .sql script in SQLite3 dump file format, for more information see my blog post here

preservedateanddatetime2*

- if this switch is not set (the default), Server columns of type "date" and "datetime2" are converted to datetime columns (which could cause data loss). If the switch is set, the columns are converted to nvarchar(10) and nvarchar(27), preventing any data loss.

keepschema
- this will create table names like "dbo.Shippers" instead of just "Shippers"

Updated Wiki: Home

ErikEJ — Thu, 10 Jan 2013 08:06:51 GMT

Project Description
This console app and SQL Server 2008 Management Studio add-in helps you better manage your SQL Compact development efforts. It allows you to script schema and data to a .sql file, which can be used in any context. It also scripts DML for use in SSMS scripts.

You can use the resulting script for documentation, programmatic scripting of SQL Compact database files, or migration of schema and data to SQL Server (Express) 2005 or later.

Notice that a similar add-in for Visual Studio 2010 (Pro or higher) for SQL Compact 3.5 and 4.0 is now available here

New features in release 3.5.2

SSMS 2008 add-in updated with all fixes in lates scripting libraries
The command line utilities and scripting library also works with SQL Server Compact 4.0
New command line switches: exclude, dataonly, diff, dgml, wpdc, sqlite - see the documentation page

ErikEJ blogs about SQL Compact, .NET and related stuff News Feed

SQL Server Compact Code Snippet of the Week #1 : locate the ROWGUIDCOL column in a table

7. januar 2013 | From ErikEJ blogs about SQL Compact, .NET and related stuff

Integrating Red Gate SmartAssembly in the SQL Server Compact Toolbox

19. december 2012 | From ErikEJ blogs about SQL Compact, .NET and related stuff

SQL Server Compact Merge Replication Library alpha released

29. november 2012 | From ErikEJ blogs about SQL Compact, .NET and related stuff

ErikEJ blogs about SQL Compact, .NET and related stuff News Feed

SQL Server Management Studio 2008 (Express) add-in

ExportSqlCE is a command line application and a SQL Server 2008 Management Studio (Express) add-in.
The add-in adds the following menu items to the table context menu in Object Explorer:
- Show Table Data (browse, sort, edit, import/export/delete images, refresh data)
- Script Table as CREATE, DROP, SELECT, INSERT, UPDATE, DELETE and INSERTs (data) to New Query Editor Windows/File/Clipboard
- Import Data from CSV
- Rename

It also adds the menu items "Script Database" and "Script Server Database" to the database context menu:

Command line utilities

Credits

The project is based on the work by Bembeng Arifin published here: http://bembengarifin-tech.blogspot.com/2008/08/generate-script-export-data-from-sql-ce.html.

Also see Related projects for other credits.

Updated Wiki: Home

ErikEJ — Thu, 10 Jan 2013 08:03:54 GMT

SSMS 2008 add-in updated with all fixes in lates scripting libraries
The command line utilities and scripting library also works with SQL Server Compact 4.0
New command line switches: exclude, dataonly, diff, dgml, wpdc, sqlite - see the documentation page

For more SQL Compact news and tips, visit my Blog

SQL Server Management Studio 2008 (Express) add-in

ExportSqlCE is a command line application and a SQL Server 2008 Management Studio (Express) add-in.
The add-in adds the following menu items to the table context menu in Object Explorer:
- Show Table Data (browse, sort, edit, import/export/delete images, refresh data)
- Script Table as CREATE, DROP, SELECT, INSERT, UPDATE, DELETE and INSERTs (data) to New Query Editor Windows/File/Clipboard
- Import Data from CSV
- Rename

It also adds the menu items "Script Database" and "Script Server Database" to the database context menu:

Command line utilities

ErikEJ blogs about SQL Compact, .NET and related stuff News Feed

SQL Server Compact Code Snippet of the Week #1 : locate the ROWGUIDCOL column in a table

7. januar 2013 | From ErikEJ blogs about SQL Compact, .NET and related stuff

Integrating Red Gate SmartAssembly in the SQL Server Compact Toolbox

19. december 2012 | From ErikEJ blogs about SQL Compact, .NET and related stuff

SQL Server Compact Merge Replication Library alpha released

29. november 2012 | From ErikEJ blogs about SQL Compact, .NET and related stuff

ErikEJ blogs about SQL Compact, .NET and related stuff News Feed

Credits

Updated Wiki: Command line utilities

ErikEJ — Wed, 02 Jan 2013 13:19:30 GMT

C:\Data\SQLCE\bin>exportsqlce
Usage :
  ExportSQLCE.exe [SQL Compact Connection String] [output file location] [exclude] [schemaonly|dataonly] [saveimages] [sqlazure]
Examples:
  ExportSQLCE.exe "Data Source=D:\Northwind.sdf;" Northwind.sql
  ExportSQLCE.exe "Data Source=D:\Northwind.sdf;" Northwind.sql exclude:Shippers,Products

Usage: (To create a schema diff script)
  ExportSQLCE.exe diff [SQL Compact or SQL Server Connection String (source)] [SQL Compact or SQL Server Connection String (target)] [output file location]
Example :
  ExportSQLCE.exe diff "Data Source=D:\Northwind.sdf;" "Data Source=.\SQLEXPRESS,Inital Catalog=Northwind" NorthwindDiff.sql

Usage: (To create a database graph)
  ExportSQLCE.exe dgml [SQL Compact or SQL Server Connection String (source)] [output file location]
Example:
  ExportSQLCE.exe dgml "Data Source=D:\Northwind.sdf;" C:\temp\northwind.dgml

Usage: (To create a Windows Phone DataContext)
  ExportSQLCE.exe wpdc [SQL Compact or SQL Server Connection String (source)] [output file location]
Example :
  ExportSQLCE.exe wpdc "Data Source=D:\Northwind.sdf;" C:\temp\Northwind.cs

Usage : (To script an entire database to SQLite format)
 ExportSQLCE.exe [SQL CE Connection String] [output file location] [sqlite]
Example:
 ExportSQLCE.exe "Data Source=D:\Northwind.sdf;" Northwind.sql sqlite

Command line for Export2SqlCE:

Usage :
 Export2SQLCE.exe [SQL Server Connection String] [output file location] [[exclude]] [[schemaonly]] [[saveimages]] [[preservedateanddatetime2]] [[keepschema]]
 (exclude, schemaonly, saveimages, keepschema and preservedateanddatetime2 are optional parameters)

Examples :
 Export2SQLCE.exe "Data Source=(local);Initial Catalog=Northwind;Integrated Security=True" Northwind.sql
 Export2SQLCE.exe "Data Source=(local);Initial Catalog=Northwind;Integrated Security=True" Northwind.sql schemaonly
 Export2SQLCE.exe "Data Source=(local);Initial Catalog=Northwind;Integrated Security=True" Northwind.sql exclude:dbo.Shippers,dbo.Suppliers

Notice that the SQL Server Export currently does not support identically named tables in different schemas.

Command line utilities optional parameters:

exclude:
- list of tables to be excluded from scripting, separated by commas - sample: exclude:dbo.Shippers,dbo.Products

schemaonly:
- this will cause the script to not contain any data, by only table and constraint definitions - so no INSERT statments in the script.

dataonly:
- this will cause the script to contain INSERT statments only.

saveimages
- this will cause all image field data to be written to individual files rather than be included in the script. The files are named <NewGuid()>.blob, and are in the same folder as the generated script. The resulting script and related files can used by SqlCeCmd to import into a SQL Compact database file. This can be useful if your database contains large image fields (5-10 MB or more), in order to avoid out of memory errors.

sqlazure
- this will cause primary keys to be scripted before any INSERT staements, batch INSERTS in a GO per 1000 statements, and removes support for ROWGUIDCOL (which is not available in SQL Azure)

diff
- this will generate a SQL Diff script based on differences between source and target data sources.

dgml
- this will generate a .dgml file and releated .sqlce/.sql files in the specified folder, that contains a diagram of the data source.

wpdc
- this will generate a .cs or .vb file with a Windows Phone specific Linq to SQL DataContext and related classes. Requires the Windows SDK version 7 to be installed.

sqlite
- this will generate a .sql script in SQLite3 dump file format, for more information see my blog post here

Updated Wiki: Command line utilities

ErikEJ — Wed, 02 Jan 2013 13:01:12 GMT

C:\Data\SQLCE\bin>exportsqlce
Usage :
  ExportSQLCE.exe [SQL Compact Connection String] [output file location] [exclude] [schemaonly|dataonly] [saveimages] [sqlazure]
Examples:
  ExportSQLCE.exe "Data Source=D:\Northwind.sdf;" Northwind.sql
  ExportSQLCE.exe "Data Source=D:\Northwind.sdf;" Northwind.sql exclude:Shippers,Products

Usage: (To create a schema diff script)
  ExportSQLCE.exe diff [SQL Compact or SQL Server Connection String (source)] [SQL Compact or SQL Server Connection String (target)] [output file location]
Example :
  ExportSQLCE.exe diff "Data Source=D:\Northwind.sdf;" "Data Source=.\SQLEXPRESS,Inital Catalog=Northwind" NorthwindDiff.sql

Usage: (To create a database graph)
  ExportSQLCE.exe dgml [SQL Compact or SQL Server Connection String (source)] [output file location]
Example:
  ExportSQLCE.exe dgml "Data Source=D:\Northwind.sdf;" C:\temp\northwind.dgml

Usage: (To create a Windows Phone DataContext)
  ExportSQLCE.exe wpdc [SQL Compact or SQL Server Connection String (source)] [output file location]
Example :
  ExportSQLCE.exe wpdc "Data Source=D:\Northwind.sdf;" C:\temp\Northwind.cs

Usage : (To script an entire database to SQLite format)
 ExportSQLCE.exe [SQL CE Connection String] [output file location] [sqlite]
Example:
 ExportSQLCE.exe "Data Source=D:\Northwind.sdf;" Northwind.sql sqlite

Command line for Export2SqlCE:

C:\Data\SQLCE\bin>export2sqlce
Usage :
 Export2SQLCE.exe [SQL Server Connection String] [output file location] [exclude] [schemaonly] [saveimages]

Examples :
 Export2SQLCE.exe "Data Source=(local);Initial Catalog=Northwind;Integrated Security=True" Northwind.sql
 Export2SQLCE.exe "Data Source=(local);Initial Catalog=Northwind;Integrated Security=True" Northwind.sql schemaonly

Notice that the SQL Server Export currently does not support identically named tables in different schemas.

Command line utilities optional parameters:

exclude:
- list of tables to be excluded from scripting, separated by commas - sample: exclude:dbo.Shippers,dbo.Products

schemaonly:
- this will cause the script to not contain any data, by only table and constraint definitions - so no INSERT statments in the script.

dataonly:
- this will cause the script to contain INSERT statments only.

saveimages
- this will cause all image field data to be written to individual files rather than be included in the script. The files are named <NewGuid()>.blob, and are in the same folder as the generated script. The resulting script and related files can used by SqlCeCmd to import into a SQL Compact database file. This can be useful if your database contains large image fields (5-10 MB or more), in order to avoid out of memory errors.

sqlazure
- this will cause primary keys to be scripted before any INSERT staements, batch INSERTS in a GO per 1000 statements, and removes support for ROWGUIDCOL (which is not available in SQL Azure)

diff
- this will generate a SQL Diff script based on differences between source and target data sources.

dgml
- this will generate a .dgml file and releated .sqlce/.sql files in the specified folder, that contains a diagram of the data source.

wpdc
- this will generate a .cs or .vb file with a Windows Phone specific Linq to SQL DataContext and related classes. Requires the Windows SDK version 7 to be installed.

sqlite
- this will generate a .sql script in SQLite3 dump file format, for more information see my blog post here

New Comment on "Scripting API samples"

ErikEJ — Wed, 05 Sep 2012 13:05:28 GMT

It is not implemented for SQL Server Compact, only SQL Server (currently)

New Comment on "Scripting API samples"

theBlaza — Wed, 05 Sep 2012 12:07:42 GMT

using (IRepository repository = Helper.CreateRepository("Data Source = '" + ResultDir + "db.sdf';")) { try { ResultDir = Environment.CurrentDirectory + @"\Result\"; if (!Directory.Exists(ResultDir)) Directory.CreateDirectory(ResultDir); repository.ExecuteSqlFile(ResultDir + "script.sql"); } catch (Exception ex) { Logs.Add(ex.Message); } } Looks like repository.ExecuteSqlFile(ResultDir + "script.sql"); wont work, do you have some update about this? Thank you

New Comment on "Command line utilities"

sandroriz — Mon, 02 Jul 2012 14:47:41 GMT

Hi Erik, I use very often you export2SqlCE tool. Normally I'm using 3.5.2.0, today I downloaded last version (3.5.2.15) and on the same DB it gives me an exception and doesn't create the script Error: System.ArgumentException: A relation already exists for these child colum ns. at System.Data.DataRelationCollection.DataSetRelationCollection.AddCore(DataR elation relation) at System.Data.DataRelationCollection.Add(DataRelation relation) at System.Data.DataRelationCollection.Add(String name, DataColumn[] parentCol umns, DataColumn[] childColumns) at ErikEJ.SqlCeScripting.Generator.FillSchemaDataSet(List`1 tables) at ErikEJ.SqlCeScripting.Generator.ExcludeTables(IList`1 tablesToExclude) at ExportSqlCE.Program.Main(String[] args) 3.5.2.0 (fortunaltely I kept a backup) works perfectly. thx

Updated Wiki: Developer tips

ErikEJ — Sat, 28 Apr 2012 09:49:23 GMT

Building
In order to build the command line utilities, IlMerge must be run, as they depend on QuickGraph.
First, run the RebuildAllExceptSetup.cmd batch file in the solution root, then run ILMExpSqlCE.cmd in the lib folder.
You may have to modify the paths to suit your environment.

Debugging

I am currently developing using SSMS 2008 R2 SP1.

To debug the add-in, configure your project as shown:

The command line for SSMS on my computer is:
C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe

Then build the solution, and right click the Setup project, and select Install.

Then press F5 to debug, and you can set breakpoints etc.

Updated Wiki: Developer tips

ErikEJ — Sat, 28 Apr 2012 09:49:11 GMT

Building
In order to build the command line utilities, IlMerge mus be run, as they depend on QuickGraph.
First, run the RebuildAllExceptSetup.cmd batch file in the solution root, then run ILMExpSqlCE.cmd in the lib folder.
You may have to modify the paths to suit your environment.

Debugging

I am currently developing using SSMS 2008 R2 SP1.

To debug the add-in, configure your project as shown:

The command line for SSMS on my computer is:
C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe

Then build the solution, and right click the Setup project, and select Install.

Then press F5 to debug, and you can set breakpoints etc.

New Comment on "Developer tips"

ErikEJ — Thu, 12 Apr 2012 17:17:50 GMT

Yes, works fine on my Win 7 x64 system with SSMS 2008 R2, not sure about debugging, though.

Updated Wiki: Developer tips

ErikEJ — Thu, 12 Apr 2012 17:17:05 GMT

Debugging

I am currently developing using SSMS 2008 R2 SP1.

To debug the add-in, configure your project as shown:

The command line for SSMS on my computer is:
C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe

Then build the solution, and right click the Setup project, and select Install.

Then press F5 to debug, and you can set breakpoints etc.

New Comment on "Developer tips"

jackandjill — Thu, 12 Apr 2012 15:23:41 GMT

Unfortunately i have only ssms08r2 is this working now since u posted this is Apr 2010?

New Comment on "Command line utilities"

cosmmin_m — Fri, 16 Mar 2012 07:59:14 GMT

Hi. Tried to run the Export2SqlCE.exe with the [dataonly] switch but the generated file contains the table definitions as well. The [schemaonly] switch works fine. Any idea what might cause this issue? Using SQL Server 2008. Thanks.

New Comment on "Scripting API samples"

ErikEJ — Sat, 03 Mar 2012 02:19:34 GMT

You nned to add a reference to this and the SqlCeScripting and/or the SqlCeScripting40 .dll

New Comment on "Scripting API samples"

neda_1982 — Fri, 02 Mar 2012 16:37:44 GMT

Hi Erik, I tried to use your code for Generating a single table script, but it gives me an error: Could not load file or assembly 'ISqlCeScripting, Version=3.5.2.0, Culture=neutral, PublicKeyToken=3681435cabd17ad2' or one of its dependencies. The system cannot find the file specified. Is there any extra code I should add? Thanks, Neda

Updated Wiki: Home

ErikEJ — Mon, 30 Jan 2012 14:29:08 GMT

SSMS 2008 add-in updated with all fixes in lates scripting libraries
The command line utilities and scripting library also works with SQL Server Compact 4.0
New command line switches: exclude, dataonly, diff, dgml, wpdc
Support for export to SQL Azure (batching, primary keys before data, no ROWGUIDCOL)

ErikEJ blogs about SQL Compact, .NET and related stuff News Feed

Review of “Windows Phone 7.5 Data Cookbook”

Tuesday, January 24, 2012 | From ErikEJ blogs about SQL Compact, .NET and related stuff

Windows Phone Local Database tip: Initializing the database

Monday, January 23, 2012 | From ErikEJ blogs about SQL Compact, .NET and related stuff

Generating a LINQ to SQL DataContext for VS Express for Windows Phone

Monday, January 16, 2012 | From ErikEJ blogs about SQL Compact, .NET and related stuff

ErikEJ blogs about SQL Compact, .NET and related stuff News Feed

Credits

Updated Wiki: Command line utilities

ErikEJ — Mon, 30 Jan 2012 10:35:47 GMT

C:\Data\SQLCE\bin>exportsqlce
Usage :
  ExportSQLCE.exe [SQL Compact Connection String] [output file location] [exclude] [schemaonly|dataonly] [saveimages] [sqlazure]
Examples:
  ExportSQLCE.exe "Data Source=D:\Northwind.sdf;" Northwind.sql
  ExportSQLCE.exe "Data Source=D:\Northwind.sdf;" Northwind.sql exclude:Shippers,Products

Usage: (To create a schema diff script)
  ExportSQLCE.exe diff [SQL Compact or SQL Server Connection String (source)] [SQL Compact or SQL Server Connection String (target)] [output file location]
Example :
  ExportSQLCE.exe diff "Data Source=D:\Northwind.sdf;" "Data Source=.\SQLEXPRESS,Inital Catalog=Northwind" NorthwindDiff.sql

Usage: (To create a database graph)
  ExportSQLCE.exe dgml [SQL Compact or SQL Server Connection String (source)] [output file location]
Example:
  ExportSQLCE.exe dgml "Data Source=D:\Northwind.sdf;" C:\temp\northwind.dgml

Usage: (To create a Windows Phone DataContext)
  ExportSQLCE.exe wpdc [SQL Compact or SQL Server Connection String (source)] [output file location]
Example :
  ExportSQLCE.exe wpdc "Data Source=D:\Northwind.sdf;" C:\temp\Northwind.cs

Command line for Export2SqlCE:

C:\Data\SQLCE\bin>export2sqlce
Usage :
 Export2SQLCE.exe [SQL Server Connection String] [output file location] [exclude] [schemaonly] [saveimages]

Examples :
 Export2SQLCE.exe "Data Source=(local);Initial Catalog=Northwind;Integrated Security=True" Northwind.sql
 Export2SQLCE.exe "Data Source=(local);Initial Catalog=Northwind;Integrated Security=True" Northwind.sql schemaonly

Notice that the SQL Server Export currently does not support identically named tables in different schemas.

Command line utilities optional parameters:

exclude:
- list of tables to be excluded from scripting, separated by commas - sample: exclude:dbo.Shippers,dbo.Products

schemaonly:
- this will cause the script to not contain any data, by only table and constraint definitions - so no INSERT statments in the script.

dataonly:
- this will cause the script to contain INSERT statments only.

saveimages
- this will cause all image field data to be written to individual files rather than be included in the script. The files are named <NewGuid()>.blob, and are in the same folder as the generated script. The resulting script and related files can used by SqlCeCmd to import into a SQL Compact database file. This can be useful if your database contains large image fields (5-10 MB or more), in order to avoid out of memory errors.

sqlazure
- this will cause primary keys to be scripted before any INSERT staements, batch INSERTS in a GO per 1000 statements, and removes support for ROWGUIDCOL (which is not available in SQL Azure)

diff
- this will generate a SQL Diff script based on differences between source and target data sources.

dgml
- this will generate a .dgml file and releated .sqlce/.sql files in the specified folder, that contains a diagram of the data source.

wpdc
- this will generate a .cs or .vb file with a Windows Phone specific Linq to SQL DataContext and related classes. Requires the Windows SDK version 7 to be installed.

Updated Wiki: Command line utilities

ErikEJ — Mon, 30 Jan 2012 10:33:36 GMT

This project contains 3 command line applications:

- ExportSqlCE - for scripting an entire SQL Server Compact 3.5 database
- ExportSqlCE31 - for scripting an entire SQL Server Compact 3.1 database
- Export2SqlCE - for scripting an entire SQL Server 2005/2008 database providing SQL Compact compatible T-SQL statements.

Command line for ExportSqlCE, ExportSqlCE40 and ExportSqlCE31:

C:\Data\SQLCE\bin>exportsqlce
Usage :
  ExportSQLCE.exe [SQL Compact Connection String] [output file location] [exclude] [schemaonly|dataonly] [saveimages] [sqlazure]
Examples:
  ExportSQLCE.exe "Data Source=D:\Northwind.sdf;" Northwind.sql
  ExportSQLCE.exe "Data Source=D:\Northwind.sdf;" Northwind.sql exclude:Shippers,Products

Usage: (To create a schema diff script)
  ExportSQLCE.exe diff [SQL Compact or SQL Server Connection String (source)] [SQL Compact or SQL Server Connection String (target)] [output file location]
Example :
  ExportSQLCE.exe diff "Data Source=D:\Northwind.sdf;" "Data Source=.\SQLEXPRESS,Inital Catalog=Northwind" NorthwindDiff.sql

Usage: (To create a database graph)
  ExportSQLCE.exe dgml [SQL Compact or SQL Server Connection String (source)] [output file location]
Example:
  ExportSQLCE.exe dgml "Data Source=D:\Northwind.sdf;" C:\temp\northwind.dgml

Usage: (To create a Windows Phone DataContext)
  ExportSQLCE.exe wpdc [SQL Compact or SQL Server Connection String (source)] [output file location]
Example :
  ExportSQLCE.exe wpdc "Data Source=D:\Northwind.sdf;" C:\temp\Northwind.cs

Command line for Export2SqlCE:

C:\Data\SQLCE\bin>export2sqlce
Usage :
 Export2SQLCE.exe [SQL Server Connection String] [output file location] [exclude] [schemaonly] [saveimages]

Examples :
 Export2SQLCE.exe "Data Source=(local);Initial Catalog=Northwind;Integrated Security=True" Northwind.sql
 Export2SQLCE.exe "Data Source=(local);Initial Catalog=Northwind;Integrated Security=True" Northwind.sql schemaonly

Notice that the SQL Server Export currently does not support identically named tables in different schemas.

Command line utilities optional parameters:

exclude:
- list of tables to be excluded from scripting, separated by commas - sample: exclude:dbo.Shippers,dbo.Products

schemaonly:
- this will cause the script to not contain any data, by only table and constraint definitions - so no INSERT statments in the script.

dataonly:
- this will cause the script to contain INSERT statments only.

saveimages
- this will cause all image field data to be written to individual files rather than be included in the script. The files are named <NewGuid()>.blob, and are in the same folder as the generated script. The resulting script and related files can used by SqlCeCmd to import into a SQL Compact database file. This can be useful if your database contains large image fields (5-10 MB or more), in order to avoid out of memory errors.

sqlazure
- this will cause primary keys to be scripted before any INSERT staements, batch INSERTS in a GO per 1000 statements, and removes support for ROWGUIDCOL (which is not available in SQL Azure)

diff
- this will generate a SQL Diff script based on differences between source and target data sources.

dgml
- this will generate a .dgml file and releated .sqlce/.sql files in the specified folder, that contains a diagram of the data source.

wpdc
- this will generate a .cs or .vb file with a Windows Phone specific Linq to SQL DataContext and related classes. Requires the Windows SDK version 7 to be installed.