Comments
Sort by recent activity
I'd suggest using ISO 8601 basic format for the file's name, like "20080208T1837Z". / comments
I'd suggest using ISO 8601 basic format for the file's name, like "20080208T1837Z".
Michelle Taylor wrote:
There's already a request in the requests list for the ability to only *compare* objects in a certain schema (which would therefore lead to only those objects being synchronized) - does that cover your requirements, jalbert?
Yes, as long as multiple schemas can be chosen at the same time. Thanks.
James / comments
Michelle Taylor wrote:
There's already a request in the requests list for the ability to only *compare* objects in a certain schema (which would therefore lead to only those objects being synchr...
How about the ability to separately choose schemas for synchronization? That implies that all objects which belong to the chosen schema(s) are synched. / comments
How about the ability to separately choose schemas for synchronization? That implies that all objects which belong to the chosen schema(s) are synched.
The problem isn't when those statements are run on SQL Server 2005. The problem happens when SQL Compare 6.2 attempts to synchronize a script that contains the code. / comments
The problem isn't when those statements are run on SQL Server 2005. The problem happens when SQL Compare 6.2 attempts to synchronize a script that contains the code.
Jonathan: I am sorry I didn't communicate that the column definition in the table DDL does indeed have the schema name of the UDT: CREATE TABLE foo
(
value VARCHAR(30) NOT NULL,
computed_value AS (CAST(value AS dbo.MyUDT))
);
While this works properly when I create the table in SQL Server Management Studio, when I try to synchronize a script using SQL Compare 6.1, the "dbo." part of the UDT's name is omitted, thus causing the aforementioned error.
I'll admit this is an unusual case. / comments
Jonathan: I am sorry I didn't communicate that the column definition in the table DDL does indeed have the schema name of the UDT:CREATE TABLE foo
(
value VARCHAR(30) NOT NULL,
comput...
This is still an issue in version 6.2. / comments
This is still an issue in version 6.2.
This is still a problem in version 6.2. I hope there are plans to fix this relatively soon; we'd like to put SQL Compare in the hands of all of our devs but this problem is holding it up. Thanks. / comments
This is still a problem in version 6.2. I hope there are plans to fix this relatively soon; we'd like to put SQL Compare in the hands of all of our devs but this problem is holding it up. Thanks.
I encountered this problem while running scripts that are being developed by hand in a text editor. It's easy enough to mess up and break references that way.
With that in mind, it would be very helpful for SQL Compare 6 to show which table(s)/view(s) it choked on, rather than just pass the NullReferenceException to the user. Thank you for considering this enhancement. / comments
I encountered this problem while running scripts that are being developed by hand in a text editor. It's easy enough to mess up and break references that way.
With that in mind, it would be very he...