June 2, 2008 at 11:51 pm
I have a peculiar situation.
We have a replication setup for a database as transactional non-updateable on SQL Server 2005. Th replication is running fine (atleast seems to be). Recently I noticed while comparing the DDLs of the two databases, that while in the publisher database the names of the objects other than the tables, namely the views, the functions and the stored procedures are enclosed in box brackets(example, [dbo].[vwName]), in the subscriber database, the names are enclosed in double quotes (example, "dbo"."vwName").
When I manually generated a script from the publisher database and applied it on the subscriber database, the two became the same.
Please help me resolving this difference. Thanks in advance.
Chandrachurh Ghosh
DBA – MS SQL Server
Ericsson India Global Services Limited
Quality is not an act, it is a habit.
June 3, 2008 at 2:10 am
waiting for help.....not yet resolved......has anyone done replication and then a SQL compare.....what do you guys get?
Is there any database property I need to set or put off?
Chandrachurh Ghosh
DBA – MS SQL Server
Ericsson India Global Services Limited
Quality is not an act, it is a habit.
June 3, 2008 at 6:31 am
Help...Help....Help....
Chandrachurh Ghosh
DBA – MS SQL Server
Ericsson India Global Services Limited
Quality is not an act, it is a habit.
June 4, 2008 at 10:15 am
Functionally this doesn't matter - both double quotes and brackets are valid delimiters for database objects when the QUOTED_IDENTIFIER option is ON. See BOL:
http://msdn.microsoft.com/en-us/library/ms176027.aspx
I'm guessing the behavior is due to how your comparison application is making its connection and scripting the table. What happens when you use Management Studio to script the table at the subscriber that your comparison app indicates has quotes for delimiters?
Kendal Van Dyke
June 5, 2008 at 10:11 am
i have scripted one of the objects from the publisher and the same was generated with box brackets. I applied the same on the subscriber database directly. Now the two objects are being shown identical......please help to resolve.....as the schema comparing is of no use otherwise....
Chandrachurh Ghosh
DBA – MS SQL Server
Ericsson India Global Services Limited
Quality is not an act, it is a habit.
June 5, 2008 at 10:48 am
June 5, 2008 at 10:59 am
Also, what are the values for QUOTED_IDENTIFIER set to at the DB, Server, and connection level for the two servers that you're trying to compare? My guess is that some combination of QUOTED_IDENTIFIER setting and the comparison tool you're using is producing the behavior that you're seeing.
We know what happens if you connect to the publisher and script the table. What happens if you use SSMS to connect to the subscriber and script out one of the tables has quotes as delimiters?
Kendal
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply