ScriptDB

New Post: -p option working?

Robsoft — Sat, 30 Aug 2008 16:30:15 GMT

I've just been trying to use this to get scripts for my database that include 'description' extended properties.

The commandline I've got is

scriptdb -con:server=127.0.0.1\sqlexpress;database=project1;trusted_connection=yes -outdir:e:\project1\dbscripts\ -p -v -ScriptAsCreate

and everything works as intended, except that I don't get extended properties output for any of my tables.

Am I doing something wrong, perhaps?

This is the current ScriptDB exe (downloaded today!) running against SQL Express 2005 v9.0.3042, Windows XP Pro SP 3.

Really hope I can get this working as this will be an incredibly useful tool.

Many thanks!

Rob

Commented Issue: invalid path

Robsoft — Sat, 30 Aug 2008 16:24:18 GMT

The working directory does not exist when bcp.exe is running for the first table. Main() is catches an invalid path exception and ScriptDb.exe fails to complete.
Comments: ** Comment from web user: Robsoft **

Is there a work-around for this at all? Thanks!

New Post: Small bug

zuby — Mon, 25 Aug 2008 14:58:09 GMT

In DatabaseScripter.cs

In "Foreign Keys" region, ln 270

WriteScript(smo.Script(), sw);

replace with

WriteScript(smo.Script(so), sw);

'Cause ScriptingOptions are never used

New Post: Sql server 2008

Bard — Thu, 21 Aug 2008 10:03:08 GMT

I managed to compile it myself with the references for SMO version 10.0.0.0

The sql-files changed, but for the better. I also had to make a small code change for it to stop exporting system assemblies.

New Post: Sql server 2008

Bard — Wed, 20 Aug 2008 08:10:10 GMT

Has anyone tried this on slq server 2008? It fails here with a complain about an unsupported database version.

Commented Issue: Stripped off schemas

cmatech — Wed, 23 Jul 2008 04:29:41 GMT

While it does script the schemas - it needs to create a folder or leave the schema name in front of the table filename.
Example:

Schema1.Table1
Schema2.Table1

These are 2 different tables, the schemas DO get scripted - but the Table1 of Schema2 is the last one to be scripted and it overwrites the existing script for Table1 of schema1.

TIA
cmatech
Comments: ** Comment from web user: cmatech **

string FileName = Path.Combine(tables, FixUpFileName(table.Schema + "." + table.Name) + ".sql");
#region Table Definition
using (StreamWriter sw = GetStreamWriter(FileName, false))
{
if (verbose)
Console.WriteLine("Scripting {0}", table.Schema + "." + table.Name);
...
...etc

Created Issue: Stripped off schemas

cmatech — Wed, 23 Jul 2008 03:59:36 GMT

Created Issue: invalid path

Bard — Thu, 03 Jul 2008 08:22:14 GMT

The working directory does not exist when bcp.exe is running for the first table. Main() is catches an invalid path exception and ScriptDb.exe fails to complete.

UPDATED RELEASE: ScriptDB 1.2 (Mar 10, 2008)

Tue, 11 Mar 2008 06:33:22 GMT

added -p switch. if you pass it, extended properties for each object will be scripted.

Patch Applied

jezemine — Tue, 11 Mar 2008 06:22:44 GMT

jezemine has applied patch #225.

Comment:
fixed this while adding code for -p switch (controls scripting of extended properties)

Source code checked in

jezemine — Tue, 11 Mar 2008 06:21:05 GMT

adding -p command line switch. if you pass -p, then extended properties for each object will be included with the object's DDL in the same file as the DDL.

NEW POST: Thanks

deusBlue — Mon, 01 Oct 2007 08:34:03 GMT

Just want to thank you VERY much for this.

NEW POST: error when we use not trusted connection to SQL server

xgreg — Wed, 05 Sep 2007 11:20:19 GMT

Hello,

It's very helpful tool for me. Thanks.
However when we use option "-d" and we don't have trusted connection to SQL server we get following error:
...
bcp.exe "db.dbo.TableName" out TableName.txt -c -T -SServerName
Exception caught in Main()
---------------------------------------
The directory name is invalid

System.ComponentModel.Win32Exception

at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at Elsasoft.ScriptDb.DatabaseScripter.ScriptTables(Boolean verbose, Database db, ScriptingOptions so, String outputDirectory, Boolean scriptData)
at Elsasoft.ScriptDb.DatabaseScripter.GenerateScript(String connStr, String outputDirectory, Boolean scriptData, Boolean verbose)
at Elsasoft.ScriptDb.Program.Main(String[] args)
---------------------------------------

I find your description about quick solution for that - it means that you use bcp tool. I change a little your program for my use and I only inform you and other people.

CREATED ISSUE: Dependencies

mgantlett — Mon, 20 Aug 2007 20:16:24 GMT

Great tool. I want to use it for database versioning. I tried the rebuild db bat script but it fails because of dependant objects not being created ahead of time.

Do you have any suggestions?

Thanks,
Mark

Patch Uploaded

neilrickards — Fri, 17 Aug 2007 09:30:04 GMT

neilrickards has uploaded a patch.

Description:
Corrected spelling of comma in usage screen

Source code checked in

jezemine — Sat, 28 Jul 2007 03:38:44 GMT

adding a .bat file to the source distribution to create a fresh db created from the scripts that ScriptDB.exe generates.

NEW POST: Security error

tfanshteyn — Wed, 18 Jul 2007 15:41:00 GMT

Are you running it from the network?

NEW POST: Security error

pjtaylor — Sat, 30 Jun 2007 10:42:10 GMT

Hi,

This is exactly the sort of tool I'm after. However, I get the following error when I try to run it:

Request for the permission of type 'System.Security.Permissions.FileIOPermission
, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxxxxx' f
ailed.

Can anyone help?

Patch Uploaded

paulrbell — Fri, 22 Jun 2007 11:58:24 GMT

paulrbell has uploaded a patch.

Description:
Fixed a path error when using TableOneFile option. Added the option SQL2000 to output for older servers. When using TableOneFile option the Foreign Keys are placed at the end of the table scripts. When using the CreateOnly option, it applies to the SPs as well. The goal of these changes were to script a 2005 database into one file and generate that database on a SQL 2000 server. All changes were noted with //June 21, 2007 and some description of the change.

Source code checked in

tfanshteyn — Fri, 08 Jun 2007 18:29:46 GMT

Option to include database context in the scripts Corrected extract for SQL 2000 SPs