User profile for kodexe – Support

Activity overview Badges (0) Posts (1) Comments (3)

Activity overview

Latest activity by kodexe

Brian Donahue wrote: The bug report is for the GUI. It creates the synchronization in the same way given the same options. And yes, it is the same code (RedGate.SqlCompare.Engine.dll) Actually, as mentioned in the original post in this topic, we've recreated situations where the command-line tool actually produces different results (in this case, the GUI tool did *not* see any changes in the target database, which means no index rebuild or table recreate was made). I'll see if I can get databases to help you see this! / comments

Brian Donahue wrote: The bug report is for the GUI. It creates the synchronization in the same way given the same options. And yes, it is the same code (RedGate.SqlCompare.Engine.dll) Actually,...

0 votes

Brian Donahue wrote: I have opened a bug about this ( SC-5219 ). The problem seems to occur when a column is both a primary key column and the unique index for a filestream at the same time. SQL Compare will filter out this index if this is the case. The fix for this may not appear for some time as it is not trivial to implement. Any idea about why the GUI version of the same tool does NOT exhibit this erroneous behavior? To a layman like me, it sounds like you just need to copy the synchronization code from SqlCompareGui.bas to SqlCompareCmd.bas. / comments

Brian Donahue wrote: I have opened a bug about this ( SC-5219 ). The problem seems to occur when a column is both a primary key column and the unique index for a filestream at the same time. SQL...

0 votes

Brian Donahue wrote: In the last case, the user sent in the scripts, but the problem could not be reproduced in-house, so we could not take further action. Despite chasing the user down about three times, we could not get in touch with him again. And this is the only time it ever happened. So we cannot even say whether or not this problem and the other problem are the same. The other critical bit of information left out from my quote was that this only happened comparing scripts to a live database. There can be some oddness because on the live side we have to do a table rebuild in some cases and on the scripts side we don't (can't?). If you could let us know if this is a live database on both sides, the schema script on both sides, and the default collation of the databases, hopefully we can reproduce it. The quote was intended to refresh your memory, not to cast blame. [image] Yes, this is a compare between two live running databases (if I understand your question correctly). There are no scripts involved (other than perhaps the generated scripts used during the operation). We haven't tried it in any other scenario. If you want us to, please advise on how that should be done. Not sure what you mean by "schema script", but here is "script as create to new query window": USE [master] GO /****** Object: Database [MyDatabase] Script Date: 08/09/2011 09:17:29 ******/ CREATE DATABASE [MyDatabase] ON PRIMARY ( NAME = N'MyDatabase', FILENAME = N'F:\db\DATA\MyDatabase.mdf' , SIZE = 1149952KB , MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB ), FILEGROUP [FileStreamGroup1] CONTAINS FILESTREAM DEFAULT ( NAME = N'Catstream', FILENAME = N'f:\db\fstream' ) LOG ON ( NAME = N'MyDatabase_log', FILENAME = N'F:\db\DATA\MyDatabase_Log.ldf' , SIZE = 353216KB , MAXSIZE = 2048GB , FILEGROWTH = 10%) GO ALTER DATABASE [MyDatabase] SET COMPATIBILITY_LEVEL = 100 GO IF (1 = FULLTEXTSERVICEPROPERTY('IsFullTextInstalled')) begin EXEC [MyDatabase].[dbo].[sp_fulltext_database] @action = 'enable' end GO ALTER DATABASE [MyDatabase] SET ANSI_NULL_DEFAULT OFF GO ALTER DATABASE [MyDatabase] SET ANSI_NULLS OFF GO ALTER DATABASE [MyDatabase] SET ANSI_PADDING OFF GO ALTER DATABASE [MyDatabase] SET ANSI_WARNINGS OFF GO ALTER DATABASE [MyDatabase] SET ARITHABORT OFF GO ALTER DATABASE [MyDatabase] SET AUTO_CLOSE OFF GO ALTER DATABASE [MyDatabase] SET AUTO_CREATE_STATISTICS ON GO ALTER DATABASE [MyDatabase] SET AUTO_SHRINK OFF GO ALTER DATABASE [MyDatabase] SET AUTO_UPDATE_STATISTICS ON GO ALTER DATABASE [MyDatabase] SET CURSOR_CLOSE_ON_COMMIT OFF GO ALTER DATABASE [MyDatabase] SET CURSOR_DEFAULT GLOBAL GO ALTER DATABASE [MyDatabase] SET CONCAT_NULL_YIELDS_NULL OFF GO ALTER DATABASE [MyDatabase] SET NUMERIC_ROUNDABORT OFF GO ALTER DATABASE [MyDatabase] SET QUOTED_IDENTIFIER OFF GO ALTER DATABASE [MyDatabase] SET RECURSIVE_TRIGGERS OFF GO ALTER DATABASE [MyDatabase] SET DISABLE_BROKER GO ALTER DATABASE [MyDatabase] SET AUTO_UPDATE_STATISTICS_ASYNC OFF GO ALTER DATABASE [MyDatabase] SET DATE_CORRELATION_OPTIMIZATION OFF GO ALTER DATABASE [MyDatabase] SET TRUSTWORTHY OFF GO ALTER DATABASE [MyDatabase] SET ALLOW_SNAPSHOT_ISOLATION OFF GO ALTER DATABASE [MyDatabase] SET PARAMETERIZATION SIMPLE GO ALTER DATABASE [MyDatabase] SET READ_COMMITTED_SNAPSHOT OFF GO ALTER DATABASE [MyDatabase] SET HONOR_BROKER_PRIORITY OFF GO ALTER DATABASE [MyDatabase] SET READ_WRITE GO ALTER DATABASE [MyDatabase] SET RECOVERY FULL GO ALTER DATABASE [MyDatabase] SET MULTI_USER GO ALTER DATABASE [MyDatabase] SET PAGE_VERIFY CHECKSUM GO ALTER DATABASE [MyDatabase] SET DB_CHAINING OFF GO The create script for the source and target databases are identical, except for the names and file names. The default collation for both databases is Finnish_Swedish_CI_AS I can also provide you with actual database backup files if needed. / comments

Brian Donahue wrote: In the last case, the user sent in the scripts, but the problem could not be reproduced in-house, so we could not take further action. Despite chasing the user down about th...

0 votes

Command-line SQL compare breaks FileStream - but not GUI

I have a table with a FileStream blob field and a PK Guid ID, declared thusly:CREATE TABLE [dbo].[MyTable]( [Id] [uniqueidentifier] ROWGUIDCOL NOT NULL, [...

2 followers 7 comments 0 votes

Total activity: 5
Last activity: February 05, 2025 13:48
Member since: February 04, 2025 15:32

Following: 0 users
Followed by: 0 users
Votes: 0
Subscriptions: 1