Comments
Sort by recent activity
Krysztof: Looks like a step in the right direction wit the latest update. Wit the previously provided style sheet my index now renders like this: USE tempdb; GO RAISERROR('dummy error message', 16, 1) WITH LOG; GO CREATE NONCLUSTERED INDEX IXF_dbo_tablename_columnname ON dbo.tablename (columnname ASC) WHERE columnname IS NOT NULL WITH
(PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF,
DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON,
ALLOW_PAGE_LOCKS = ON) ON FG_Filegroupname; GOHowever, my constraint example still looks like this: ALTER TABLE dbo.PHEAA_master_SD ADD CONSTRAINT UQ_dbo_PHEAA_master_SD_CREATEDATE_BSSN_SEQ_PROGRAM_GUARANTOR_CURROWN_OWNERBOND UNIQUE NONCLUSTERED
(CREATEDATE ASC, BSSN ASC, SEQ ASC, PROGRAM ASC, GUARANTOR ASC, CURROWN
ASC, OWNERBOND ASC) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF
, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF
, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON
, FILLFACTOR = 70) ON PS_SLServ_MR50(CREATEDATE);For the Schema (DDL) Parentheses I selected "Compact, simple", looks like the DDL statements do not include indexes/constraints? / comments
Krysztof:Looks like a step in the right direction wit the latest update. Wit the previously provided style sheet my index now renders like this:USE tempdb;GORAISERROR('dummy error message', 16, 1) ...
Fabiola:
Here's another example of where I think the style sheet doesn't handle indexes well
ALTER TABLE dbo.PHEAA_master_SD
ADD CONSTRAINT UQ_dbo_PHEAA_master_SD_CREATEDATE_BSSN_SEQ_PROGRAM_GUARANTOR_CURROWN_OWNERBOND UNIQUE NONCLUSTERED
(CREATEDATE ASC, BSSN ASC, SEQ ASC, PROGRAM ASC, GUARANTOR ASC, CURROWN ASC, OWNERBOND ASC) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF
, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF
, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON
, FILLFACTOR = 70) ON PS_SLServ_MR50(CREATEDATE);
I would have expected that the Schema (DDL) CREATE/ALTER section also covers for example indexes, that does not seem to be the case. I would haev expected something more like this result:
USE SLServ;
GO
ALTER TABLE dbo.PHEAA_master_SD
ADD CONSTRAINT UQ_dbo_PHEAA_master_SD_CREATEDATE_BSSN_SEQ_PROGRAM_GUARANTOR_CURROWN_OWNERBOND UNIQUE NONCLUSTERED
(CREATEDATE ASC
, BSSN ASC
, SEQ ASC
, PROGRAM ASC
, GUARANTOR ASC
, CURROWN ASC
, OWNERBOND ASC)
WITH (PAD_INDEX = OFF
, STATISTICS_NORECOMPUTE = OFF
, SORT_IN_TEMPDB = OFF
, IGNORE_DUP_KEY = OFF
, ONLINE = OFF
, ALLOW_ROW_LOCKS = ON
, ALLOW_PAGE_LOCKS = ON
, FILLFACTOR = 70)
ON PS_SLServ_MR50(CREATEDATE);
GO
/ comments
Fabiola:
Here's another example of where I think the style sheet doesn't handle indexes well
ALTER TABLE dbo.PHEAA_master_SD
ADD CONSTRAINT UQ_dbo_PHEAA_master_SD_CREATEDATE_BSSN_SEQ_PROGRAM_GUARAN...
I definitely like the new feature / comments
I definitely like the new feature
I would respectfully disagree that a disabled index is a non-critical issue when comparing two databases. If I am replicating a database to another system, e.g. for performance tuning, and Red-Gate tells me the databases are identical then I would not assume I have to check whether a specific index may be disabled on one system or the other. I now have to question what else has been deemed non-critical and thus hides database structure differences from me. / comments
I would respectfully disagree that a disabled index is a non-critical issue when comparing two databases. If I am replicating a database to another system, e.g. for performance tuning, and Red-Gate...
[image]
Well, you could always retain the # objects in the project file after the first run. As long as there are only minor changes to the # objects you'd be fine, and in case of large # of changes, you'd still have the 100% cap in place. / comments
Well, you could always retain the # objects in the project file after the first run. As long as there are only minor changes to the # objects you'd be fine, and in case of large # of changes, you'...
This appears to be fixed in 12.0.39.3632. Though, seeing that the progress display now stays at 100% for long periods of time makes the cynic in me think that it's just a cosmetic change in that you cap the display of percentages at 100% [image] / comments
This appears to be fixed in 12.0.39.3632. Though, seeing that the progress display now stays at 100% for long periods of time makes the cynic in me think that it's just a cosmetic change in that yo...
Just for everybody's benefit, the code below the "SELECT query run by SQL DataCompare 12.0.32.3340" section is what SQL DataCompare runs against the SQL Server instance when it it is retrieving data for the comparison. It was retrieved via Adam Machanic's sp_WhoIsActive stored procedure. / comments
Just for everybody's benefit, the code below the "SELECT query run by SQL DataCompare 12.0.32.3340" section is what SQL DataCompare runs against the SQL Server instance when it it is retrieving dat...
This item is resolved as the root cause is a Microsoft issue to begin with and Re-Gate works around this by utilizing VARBINARY(MAX) for the comparison of certain date-time data types. / comments
This item is resolved as the root cause is a Microsoft issue to begin with and Re-Gate works around this by utilizing VARBINARY(MAX) for the comparison of certain date-time data types.
This issue is fixed in the latest version 12.0.34 / comments
This issue is fixed in the latest version 12.0.34
SQL Data Compare v12.0.32.3340
Script to reproduce:
USE tempdb;
GO
IF EXISTS ( SELECT 1
FROM sys.objects
WHERE object_id = OBJECT_ID(N'[dbo].[RedGateTableC1]')
AND type IN (N'U') )
DROP TABLE dbo.RedGateTableC1;
SET ANSI_NULLS, QUOTED_IDENTIFIER, ANSI_PADDING ON;
GO
CREATE TABLE dbo.RedGateTableC1 (id INT IDENTITY(1, 12)
NOT NULL
, ColumnA VARCHAR(20) NOT NULL
, ColumnB VARCHAR(20) NOT NULL
, PRIMARY KEY CLUSTERED (id ASC) ON [PRIMARY])
ON
[PRIMARY];
GO
Then I compare the same table on the same system with itself after manually mapping ColumnA to ColumnB. Afterwards, I manually select the manually mapped column comparison of ColumnA/ColumnB so that the only comparison would happen on the ID primary key field. If I then re-check the selected comparison columns my manually mapped column is selected again. / comments
SQL Data Compare v12.0.32.3340
Script to reproduce:
USE tempdb;
GO
IF EXISTS ( SELECT 1
FROM sys.objects
WHERE object_id = OBJECT_ID(N'[dbo].[RedGateTableC1]')
AND type IN (N'U') )
DROP TABLE...