Red Gate forums: SQL Packager 6

RE: Handling Nested Sql scripts possible with RedGate ?

Manfred.Castro — Thu, 02 May 2013 15:23:43 GMT

I don't believe that this particular tool will work in your use case.
You may want to check out our other product the SQL Comparison SDK.
http://www.red-gate.com/products/sql-development/sql-comparison-sdk/
This tool allows you to use SQL Packagers API to create your own application.

RE: Corruption of accented characters using Packager 6.6.0347

Chris.Allen — Thu, 02 May 2013 13:03:10 GMT

This is usually a function of the underlying text encoding (for example ANSI vs Unicode (UTF xx).

*My* way of solving this is, using a free text editor such as Notepad ++, check the encoding of the original text files- test if it works better when they are all UTF or all ANSI.

I hope that helps.

RE: Handling Nested Sql scripts possible with RedGate ?

bahrani — Thu, 02 May 2013 08:09:42 GMT

Thanks for your inputs

Yes regarding arguments while generating .exe for .sql script I was trying to pass arguments to SQL Packager with .sql script itself but as you rightly mentioned i was not able to do so.

So i thought lets generate the .exe first and then there might be some provision to pass arguments to the .exe which gets generated with the help of SQL Packager (with .sql script as input to SQL Packager) but later on after obtaining the .exe from SQL Packager i realised that we can pass only some predefined fixed arguments to .exe (like servername, databasename, username, password, makedatabase or makeupgrade, presql, postsql)

Also the requirement is such that the values of the arguments gets generated at runtime based on the user inputs and hence values of arguments are not fixed so keeping arguments internally within the script with fixed values will not satify our requirement

So what i understand from your inputs and with some hands on is that we cannot handle the scenario with the SQL packager wherein .sql scripts needs some arguments as inputs, right ?

Correct me if i am wrong

Thanks,
Ishant

RE: Handling Nested Sql scripts possible with RedGate ?

Manfred.Castro — Wed, 01 May 2013 17:57:29 GMT

Unfortunately I was unable to find previous instances where SQL Packager was used in this manner, so I can't say for certain that it will work.
One thing that concerns me is how do you intend to pass arguments to SQL packager since that is not supported. I suppose if the arguments were supplied within the script itself it may work.
I would suggest you try it for yourself, to see if the tool for work for you in this use case.

Corruption of accented characters using Packager 6.6.0347

chris.king@uk.g4s.com — Wed, 01 May 2013 09:58:12 GMT

Hi Folks,

I have a SQL Script that I am attempting to package that is currently 239, 343 lines in length.

The majority of this is reference data so that data script generated by the packager is about 85% of the total length.

My source script contains both English and French text and this includes accented characters such as �.

When I install from my source script to a SQL 2012 instance, the accented characters are preserved but when I package the script into an .exe using Packager the resulting installation has replaced the accented characters with question marks.

Has this behaviour been observed before? Is there anything I can do to prevent this?

TIA,

Chris King

Handling Nested Sql scripts possible with RedGate ?

bahrani — Tue, 30 Apr 2013 13:35:05 GMT

Hi,

I have one scenario wherein i have one sql script (Main.sql) to which i pass some arguments and execute the sql script using SQLCMD command
(e.g.
SQLCMD -S %1 -U %2 -P %3 -d %4 -i Main.sql -v Argument1="%4" -v Argument2="%5" -v Argument3="%4" -v filepath="%CD%" -o sql_Log_Module.txt)

This sql script (Main.sql) internally calls some more sql scripts and these internal nested scripts use the parameters passed to the main script i.e., "Main.sql" (mentioned above)

Internal scripts also have the stored procedures which gets executed

Currently we execute sql script (Main.sql) directly in batch file with the help of SQLCMD command, but we are thinking to use Red Gate (SQL Packager) instead of SQLCMD in batch file

It will be great if you provide some inputs on whether this can be done with the help of RedGate or not, i mean to say whether this is possible with the help of RedGate or not

Thanks in advance,
Ishant

RE: Creating EXE with multiple scripts and custom commandline

bahrani — Tue, 30 Apr 2013 13:33:15 GMT

RE: SQL 2012 - Compatible??

dw5304 — Tue, 02 Apr 2013 19:54:59 GMT

having same issue as listed above with patch 6.6.0.347 any eta on fix?

RE: SQL Packager dacpac file type support

stanori — Fri, 29 Mar 2013 14:35:57 GMT

Hi Hardik,

Thanks for your post. Unfortunatley, SQL Packager does not support this particular file type. I will submit a feature request on your behalf. Thanks for your suggestion and question.

Best Regards,
Steve

SQL Packager dacpac file type support

Hardik — Thu, 28 Mar 2013 13:06:40 GMT

I am using SQL Packager v 6.6.0.347.

Is there any way to use SQL Packager with dacpac file type (generated through database project build)?

RE: Error: 'fillfactor' is not a recognized CREATE TYPE option.

eddie davis — Mon, 25 Mar 2013 15:31:02 GMT

Hi AdamY

Sorry that you have encountered a problem.

I can confirm that this is a bug, I was able to reproduce the error using both V6.4.0.8 and V6.6.0.347.

The bug reference number is SPA-601, sadly I cannot provide an ETA as to when this bug will be eventually fixed. I will be maintaining a "watch" on the bug report I submitted so I can be alerted on any changes to the Bug Report and provide an update.

The workaround I can advise is to continue editing the script to remove the WITH (FILLFACTOR=90) before building the exe file.

Many Thanks
Eddie

RE: Error: 'fillfactor' is not a recognized CREATE TYPE option.

AdamY — Fri, 22 Mar 2013 18:10:24 GMT

SQL Source Control used to have this same issue and does not now - so it seems it was a bug they found and corrected.

Should I send a DB backup or is that a waste of time? I won't take the time to put one together if Red Gate isn't going to look at it.

Just so you know I'm not crazy:

RE: Error: 'fillfactor' is not a recognized CREATE TYPE option.

Brian Donahue — Fri, 22 Mar 2013 14:02:31 GMT

Sorry to say again, I can't reproduce the same behavior. Either with ignore fillfactor on or off.

RE: Error: 'fillfactor' is not a recognized CREATE TYPE option.

AdamY — Thu, 21 Mar 2013 16:36:20 GMT

When I run SQL Packager to generate a script or package, it generates code that has WITH (FILLFACTOR=90) included. I have to manually remove the WITH (FILLFACTOR=90) code first and then package that script.

Here is definition of one of the types I'm having the problem with:

Code:

CREATE TYPE [LockNeedList] AS TABLE
(
[NeedKey] [varchar](9) NOT NULL,
[NeedType] [varchar](6) NOT NULL,
PRIMARY KEY CLUSTERED ([NeedKey] ASC)
)

Again, the code generated by SQL Packager has WITH (FILLFACTOR=90) added on.

RE: type initializer in RedGate.Compression.ZLib.ZLibUtil

james.billings — Thu, 21 Mar 2013 14:18:23 GMT

Thanks for your post. This isn't a common error as far as I can tell.

Out of interest, does this just affect one user/machine? i.e. the same package runs fine elsewhere? If so, it may be a problem such as a missing/corrupt .NET Framework. Most of our tools require .NET 3.5 SP1, can you ensure that's installed on the relevant machine (same goes for .NET 2.0)?