This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- BUG in SQL Script generator
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 15, 2009
09:43 AM
BUG in SQL Script generator
Hi,
I just had to find out that there's a bug in the SQL script generator.
IS 2010 creats a tablecolumn using this statement:
SQL Management Studio 2008 creates the same column using this correct statement:
Using -1 instead of MAX forces the SQL script to fail, the script also didn't pass the Management Studio syntax test.
I had some real "fun" figuring that bug out 😞
Greetings,
Gøran
I just had to find out that there's a bug in the SQL script generator.
IS 2010 creats a tablecolumn using this statement:
- [Buffer] [varbinary] (-1) NULL
SQL Management Studio 2008 creates the same column using this correct statement:
- [Buffer] [varbinary] (MAX) NULL
Using -1 instead of MAX forces the SQL script to fail, the script also didn't pass the Management Studio syntax test.
I had some real "fun" figuring that bug out 😞
Greetings,
Gøran
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 16, 2009
12:02 AM
This is a known issue and it has been filed under the work order #IOA-000028493 to take into consideration for a future release.
The problem is that the Microsoft SQL Server Distributed Management Objects (SQL-DMO) used for the Database Import functionality does not recognize that data type. We will probably need to rewrite the functionality using Microsoft SQL Server Management Objects (SQL-SMO).
The way around this issue is to use the Text Replacement feature to replace:
[varchar] (-1) with [varchar] (max)
[nvarchar] (0) with [nvarchar] (max)
Regards.
The problem is that the Microsoft SQL Server Distributed Management Objects (SQL-DMO) used for the Database Import functionality does not recognize that data type. We will probably need to rewrite the functionality using Microsoft SQL Server Management Objects (SQL-SMO).
The way around this issue is to use the Text Replacement feature to replace:
[varchar] (-1) with [varchar] (max)
[nvarchar] (0) with [nvarchar] (max)
Regards.