Showing posts with label rtm. Show all posts
Showing posts with label rtm. Show all posts

Friday, March 30, 2012

Microsoft SQL Server 2005 RTM merge replication issues

We are trying to implement merge replication between 2 servers. Database size is around 11GB.

When I tried to create publication, snaphot agent is failing with following errror.

Error: 14151, Severity: 18, State: 1.
Replication-Replication Snapshot Subsystem: agent NBTENTSQL1X-PayDirectWeb-PayDirectPub-2 failed. The
replication agent had encountered an exception.
Source: Replication
Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentSqlException
Exception Message: String or binary data would be truncated.
Cannot find the object 'MSmerge_sel_4D388

The table where the snapshot is breaking contains around 169 columns. Can someone please help me get through this error ?

Are you using vertical partitioning to replicate subset of the columns of the table? You may be hitting an known issue in Microsoft SQL Server 2005 where the list of column names for the table is longer than 4K and hence gets truncated in an internal proc.

|||

Thanks Sudarshan, your reply is very helpful. No we are not using vertical partitioning.

If this is a known issue, did Microsoft have any immediate fix for it or we have wait for SQL2K5 SP2 ?

|||Please wait for SQL2K5 SP2. You can install the latest CTPs availalbe and test out that your scenarios works. If not, please reply back and we can take a look further.|||This is a known issue in SQL2K5 SP1 which is fixed in SP2.|||Does the same limitation apply to the complexity of joined tables in the filter? I'm getting an error in the snapshot agent, saying:

String or

binary data would be truncated.

Cannot find

the object 'MSmerge_ctsv_2C675AF5938E4EA1B7D0DCFF9ECAD9EB', because it does not

exist or you do not have permission.

sp_MS_marksystemobject:

Invalid object name '[dbo].[MSmerge_upd_2C675AF5938E4EA1B7

But this only happens when I add too many joined tables to the filter section of the publication.

Dan

Microsoft SQL Server 2005 RTM merge replication issues

We are trying to implement merge replication between 2 servers. Database size is around 11GB.

When I tried to create publication, snaphot agent is failing with following errror.

Error: 14151, Severity: 18, State: 1.
Replication-Replication Snapshot Subsystem: agent NBTENTSQL1X-PayDirectWeb-PayDirectPub-2 failed. The
replication agent had encountered an exception.
Source: Replication
Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentSqlException
Exception Message: String or binary data would be truncated.
Cannot find the object 'MSmerge_sel_4D388

The table where the snapshot is breaking contains around 169 columns. Can someone please help me get through this error ?

Are you using vertical partitioning to replicate subset of the columns of the table? You may be hitting an known issue in Microsoft SQL Server 2005 where the list of column names for the table is longer than 4K and hence gets truncated in an internal proc.

|||

Thanks Sudarshan, your reply is very helpful. No we are not using vertical partitioning.

If this is a known issue, did Microsoft have any immediate fix for it or we have wait for SQL2K5 SP2 ?

|||Please wait for SQL2K5 SP2. You can install the latest CTPs availalbe and test out that your scenarios works. If not, please reply back and we can take a look further.|||This is a known issue in SQL2K5 SP1 which is fixed in SP2.|||Does the same limitation apply to the complexity of joined tables in the filter? I'm getting an error in the snapshot agent, saying:

String or

binary data would be truncated.

Cannot find

the object 'MSmerge_ctsv_2C675AF5938E4EA1B7D0DCFF9ECAD9EB', because it does not

exist or you do not have permission.

sp_MS_marksystemobject:

Invalid object name '[dbo].[MSmerge_upd_2C675AF5938E4EA1B7

But this only happens when I add too many joined tables to the filter section of the publication.

Dan

Monday, March 12, 2012

Mgmt Studio not supporting 7.0?

I tried using Mgmt Studio RTM to connect to SQL Server 7.0 instance and
received this:
"This version of Microsoft SQL Server Management Studio can only be used to
connect to SQL Server 2005 and SQL Server 2000 servers (ConnectionDlg)"
I thought Mgmt Studio was going to support 7.0?
Hi
No. 7.0 is really very close to end of life so no support for it.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Johnny Ortega" <john.ortega@.quest.com> wrote in message
news:uuklBLx5FHA.2956@.TK2MSFTNGP12.phx.gbl...
>I tried using Mgmt Studio RTM to connect to SQL Server 7.0 instance and
> received this:
> "This version of Microsoft SQL Server Management Studio can only be used
> to
> connect to SQL Server 2005 and SQL Server 2000 servers (ConnectionDlg)"
> I thought Mgmt Studio was going to support 7.0?
>
|||Maybe part of the confusion is because the book 'Microsoft SQL Server 2005 -
Changing the Paradigm' mentions that SQL Server 7 will be supported (page
97).
Ben Nevarez
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:usTkijx5FHA.2628@.TK2MSFTNGP11.phx.gbl...
> Hi
> No. 7.0 is really very close to end of life so no support for it.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Johnny Ortega" <john.ortega@.quest.com> wrote in message
> news:uuklBLx5FHA.2956@.TK2MSFTNGP12.phx.gbl...
>
|||Hi
Lots of features get dropped from the Product over it's development life.
This support was dropped very early. SMO support for SQL Server 7.0 was
dropped very late and there is still documentation mentioning it.
During the development program, even e-mails were stale by the time most
people read them, let alone printed books.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:e2lMdML6FHA.1000@.tk2msftngp13.phx.gbl...
> Maybe part of the confusion is because the book 'Microsoft SQL Server
> 2005 - Changing the Paradigm' mentions that SQL Server 7 will be supported
> (page 97).
> Ben Nevarez
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:usTkijx5FHA.2628@.TK2MSFTNGP11.phx.gbl...
>