Community Forums
Page 1 of 2 12 LastLast
Results 1 to 5 of 6

Thread: Error using Database Import Wizard

  1. #1
    Join Date
    Jun 2013
    Posts
    51

    Error using Database Import Wizard

    Error while generating script: "[Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near '*='. (102)"

  2. #2
    Join Date
    Oct 2001
    Location
    Itasca, IL
    Posts
    2,394
    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.
    Last edited by hidenori; 08-12-2013 at 12:31 PM.
    Hidenori Yamanishi - Senior Software Engineer - Flexera Software: InstallShield Team

  3. #3
    Join Date
    May 2007
    Location
    Eden Praire, MN
    Posts
    687
    How about downloading and installing SQLServer2005_BC.msi? Just pick the DMO feature.

  4. #4
    Join Date
    Jan 2014
    Posts
    1
    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!

  5. #5
    Join Date
    Jul 2011
    Posts
    47
    InstallSiheld 2016 still does not support Script database users and database roles??

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •