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
- :
- Re: Error using Database Import Wizard
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 26, 2013
12:17 PM
Error using Database Import Wizard
Error while generating script: "[Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near '*='. (102)"
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 31, 2013
12:58 PM
To import databases from Microsoft SQL Servers, InstallShield uses the SQL Database Management Objects (SQL-DMO) which does not support Database Engine features introduced after SQL Server 2000.
For now, only a thing you can do to avoid the "Incorrect syntax near '*='. (102)" error is deselecting the "Script database users and database roles" check box on the Advanced Scripting Options panel in the Database Import Wizard.
The work order #IOA-000075349 has already been submitted to track this issue.
Sorry for the inconvenience this may have caused.
For now, only a thing you can do to avoid the "Incorrect syntax near '*='. (102)" error is deselecting the "Script database users and database roles" check box on the Advanced Scripting Options panel in the Database Import Wizard.
The work order #IOA-000075349 has already been submitted to track this issue.
Sorry for the inconvenience this may have caused.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 31, 2013
01:37 PM
How about downloading and installing SQLServer2005_BC.msi? Just pick the DMO feature.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 16, 2014
11:49 PM
I got the same Error: Error while generating script: "[Microsoft][ODBC SQL Server Driver][SQL Server]Falsche Syntax in der Nähe von '*'. (102)"
I do this Settings in the Database Import Wizzard:
Objects to Script: no selection
Scripting Options: Create Only if Missing, Script Indexes, Script-Full-Text-Indexes, Script Triggers, Script Check Constraints, Script Foreign Keys, Script Primary Keys, Script Defaults
Advanced Scripting Options: File Format: Unicode
The Table to Import:
CREATE TABLE [dbo].[Appointments] (
[UniqueID] int IDENTITY(1, 1) NOT NULL,
[Type] int NULL,
[StartDate] smalldatetime NULL,
[EndDate] smalldatetime NULL,
[AllDay] bit NULL,
[Subject] nvarchar(50) COLLATE Latin1_General_CI_AS NULL,
[Location] nvarchar(50) COLLATE Latin1_General_CI_AS NULL,
[Description] nvarchar(max) COLLATE Latin1_General_CI_AS NULL,
[Status] int NULL,
[Label] int NULL,
[ResourceID] int NULL,
[ResourceIDs] nvarchar(max) COLLATE Latin1_General_CI_AS NULL,
[ReminderInfo] nvarchar(max) COLLATE Latin1_General_CI_AS NULL,
[RecurrenceInfo] nvarchar(max) COLLATE Latin1_General_CI_AS NULL,
[AMSID] bigint DEFAULT 0 NULL,
CONSTRAINT [PK_Appointments] PRIMARY KEY CLUSTERED ([UniqueID])
WITH (
PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF, STATISTICS_NORECOMPUTE = OFF,
ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON)
)
ON [PRIMARY]
GO
The Error only Appers in InstallShield 2013. In InstallShield 12 this has worked!
I do this Settings in the Database Import Wizzard:
Objects to Script: no selection
Scripting Options: Create Only if Missing, Script Indexes, Script-Full-Text-Indexes, Script Triggers, Script Check Constraints, Script Foreign Keys, Script Primary Keys, Script Defaults
Advanced Scripting Options: File Format: Unicode
The Table to Import:
CREATE TABLE [dbo].[Appointments] (
[UniqueID] int IDENTITY(1, 1) NOT NULL,
[Type] int NULL,
[StartDate] smalldatetime NULL,
[EndDate] smalldatetime NULL,
[AllDay] bit NULL,
[Subject] nvarchar(50) COLLATE Latin1_General_CI_AS NULL,
[Location] nvarchar(50) COLLATE Latin1_General_CI_AS NULL,
[Description] nvarchar(max) COLLATE Latin1_General_CI_AS NULL,
[Status] int NULL,
[Label] int NULL,
[ResourceID] int NULL,
[ResourceIDs] nvarchar(max) COLLATE Latin1_General_CI_AS NULL,
[ReminderInfo] nvarchar(max) COLLATE Latin1_General_CI_AS NULL,
[RecurrenceInfo] nvarchar(max) COLLATE Latin1_General_CI_AS NULL,
[AMSID] bigint DEFAULT 0 NULL,
CONSTRAINT [PK_Appointments] PRIMARY KEY CLUSTERED ([UniqueID])
WITH (
PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF, STATISTICS_NORECOMPUTE = OFF,
ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON)
)
ON [PRIMARY]
GO
The Error only Appers in InstallShield 2013. In InstallShield 12 this has worked!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 06, 2017
10:40 PM
InstallSiheld 2016 still does not support Script database users and database roles??
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 06, 2017
10:43 PM
Could Flexera possibly remove functions it does not support so I don't get a unhelpful error message like
Error while generating script: "[Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near '*'. (102)"
When using the option "Script Defaults".
Error while generating script: "[Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near '*'. (102)"
When using the option "Script Defaults".