Script generation is crashing on win7 pro 32 bit

May 19, 2010 at 6:11 PM
Edited May 19, 2010 at 6:27 PM

V3.2.2 is crashing while generating migration scripts. I have created raw database using MSSQLEXpress 2008 R2 with following two parameter set and tried to generate migration script for SQLAzure using all default options. It crashes all the time when I generate the scripts, is this known issue?

ANSI NULLS Enabled = true 

Quoted Identifiers Enabled = true 

 

May 20, 2010 at 9:14 AM

Have you got a stack trace or error message?

May 20, 2010 at 7:32 PM

This is the error I get -

[Window Title]
SQLAzureMW

[Main Instruction]
SQLAzureMW has stopped working

[Content]
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.

[Close program]

 

 

Coordinator
May 24, 2010 at 2:39 AM

Hi,

I am running Windows 7 pro 32 bit as well, so that souldn't be a problem.  When you say you have two parameters set (ANSI NULLS and Quoted Identifiers), where do you have them set? I will need to try and reproduce the issue you are having.  Would it be possible for you to script your database and contact me through codeplex so that we can discuss this offline?

Regards,
George

May 24, 2010 at 5:59 PM

Open SQLExpress 2008 R2 management studio. While create new database, go to options page and set following properties under Miscellaneous section.

ANSI NULLS Enabled = true 

Quoted Identifiers Enabled = true 

Here is the create script I generated using SQLExpress R2 management studio -

USE [master]
GO

/****** Object:  Database [test_empty]    Script Date: 05/24/2010 09:29:27 ******/
CREATE DATABASE [test_empty] ON  PRIMARY
( NAME = N'test_empty', FILENAME = N'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\test_empty.mdf' , SIZE = 2048KB , MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB )
 LOG ON
( NAME = N'test_empty_log', FILENAME = N'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\test_empty_log.ldf' , SIZE = 1024KB , MAXSIZE = 2048GB , FILEGROWTH = 10%)
GO

ALTER DATABASE [test_empty] SET COMPATIBILITY_LEVEL = 100
GO

IF (1 = FULLTEXTSERVICEPROPERTY('IsFullTextInstalled'))
begin
EXEC [test_empty].[dbo].[sp_fulltext_database] @action = 'enable'
end
GO

ALTER DATABASE [test_empty] SET ANSI_NULL_DEFAULT OFF
GO

ALTER DATABASE [test_empty] SET ANSI_NULLS ON
GO

ALTER DATABASE [test_empty] SET ANSI_PADDING OFF
GO

ALTER DATABASE [test_empty] SET ANSI_WARNINGS OFF
GO

ALTER DATABASE [test_empty] SET ARITHABORT OFF
GO

ALTER DATABASE [test_empty] SET AUTO_CLOSE OFF
GO

ALTER DATABASE [test_empty] SET AUTO_CREATE_STATISTICS ON
GO

ALTER DATABASE [test_empty] SET AUTO_SHRINK OFF
GO

ALTER DATABASE [test_empty] SET AUTO_UPDATE_STATISTICS ON
GO

ALTER DATABASE [test_empty] SET CURSOR_CLOSE_ON_COMMIT OFF
GO

ALTER DATABASE [test_empty] SET CURSOR_DEFAULT  GLOBAL
GO

ALTER DATABASE [test_empty] SET CONCAT_NULL_YIELDS_NULL OFF
GO

ALTER DATABASE [test_empty] SET NUMERIC_ROUNDABORT OFF
GO

ALTER DATABASE [test_empty] SET QUOTED_IDENTIFIER ON
GO

ALTER DATABASE [test_empty] SET RECURSIVE_TRIGGERS OFF
GO

ALTER DATABASE [test_empty] SET  DISABLE_BROKER
GO

ALTER DATABASE [test_empty] SET AUTO_UPDATE_STATISTICS_ASYNC OFF
GO

ALTER DATABASE [test_empty] SET DATE_CORRELATION_OPTIMIZATION OFF
GO

ALTER DATABASE [test_empty] SET TRUSTWORTHY OFF
GO

ALTER DATABASE [test_empty] SET ALLOW_SNAPSHOT_ISOLATION OFF
GO

ALTER DATABASE [test_empty] SET PARAMETERIZATION SIMPLE
GO

ALTER DATABASE [test_empty] SET READ_COMMITTED_SNAPSHOT OFF
GO

ALTER DATABASE [test_empty] SET HONOR_BROKER_PRIORITY OFF
GO

ALTER DATABASE [test_empty] SET  READ_WRITE
GO

ALTER DATABASE [test_empty] SET RECOVERY SIMPLE
GO

ALTER DATABASE [test_empty] SET  MULTI_USER
GO

ALTER DATABASE [test_empty] SET PAGE_VERIFY CHECKSUM 
GO

ALTER DATABASE [test_empty] SET DB_CHAINING OFF
GO


 

Coordinator
May 25, 2010 at 5:03 PM

Hmmmm, it is a WOM (work on my machine).  I ran your script, created the test database and run SQLAzureMW on it.  SQLAzureMW didn't generate any script, because there were no table, stored proc, UDT, ....  So, I don't know why it is not working on your machine.  Have you tried something like a Northwind, Pubs, or some other database?  Anyway. if we can figure out how to reproduce the issue your having, I will be able to help you out.  Let me know if you have any suggestions for me to try.

Regards,
George