Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog


Channel Description:

Discussions on SQL Server Replication

older | 1 | .... | 37 | 38 | (Page 39) | 40 | 41 | .... | 181 | newer

    0 0

    Hello, we made a short term solution of replication for reporting into a permanent solution and I am wanting to head off traffic/bandwidth issues I see potentially coming due to our continued and increased use of replication. We are using transactional replication to create reporting versions of our application oltp databases. To save time we took the approach to replicate the entire table when it was needed for a report rather than requiring the developers to identify columns needed and also to have the data available as we were creating a large number of reports in short order. Now I am thinking I should require the developers to spell out the columns they need rather than all columns in a table. Can anyone tell me, besides the obvious that it is "easier", what any downside would be to only replicating certain columns in a table? It makes sense to me to approach in this manner.

    Thanks


    0 0

    Hi All

    Need a answer definitive answer on the following .

    We are looking at having two geographically located SQL servers. They will be connected via a 1GB link and be on different subnets

    What i want to know is do we require storage based replication in order for the SQL "Always on " to work ?

    Thanks!


    frank


    0 0

    I found a relative post very interesting

    http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/b73b6568-dc34-4c89-9979-7f9a0c8e1dc5

    but need some more information on this topic.

    "regularly scans the T-Log"  What about the latency? less than 3 seconds?

    I need to assess these solutions in terms of license fees and compliance to our needs.

    1a: SSIS: Integration Services as ETL for CDC purpose

    1b: Replication feature: mirroring (Primary, Mirror ans Witness)

    2: Talend Integration Suite as ETL for Change Data Capture

    We can not afford clustering.

    Our specific configuration applies to a very small network of WinXP workstation machines in a WORKGROUP (from 2 to 5 machines)

    Dealing with a very small database (one hundred of tables): we need to synchronize 30 tables; most of them contains less than 100 rows! some historical tables contain a maximum of 200 000 rows. That's why we work with the Express version of SQLServer!

    However we need to have a backUp database in case the primary machines crashes, with very few latency as far as synchronization is concerned. The mirror machine would take the role of the previous primary one (same IP, same ftp server synchronized, same software).

    Role changes should operate in less than 5 minutes after the mirror machines restarts (changing IP, launching database and so on).

    Any comments about the pros and cons of these solutions?

    The primary machines serves database access on the workgroup. The mirror machine could stop and restart and need to retrieve missing information. How does it works with SIIS/CDC and with mirroring feature (SQL Agent) when the "mirror" machines restarts? redo logs to get back missing data?

    Kind regards

    JNB


    0 0

    Can anyone suggest me steps to configure transactional replication without  Active Directory??


    sadankumar


    0 0

     

    Hi All,

     

    i am doing Merge and Transaction Replication in MSSQL Server 2000,

     

    but i have no Idea how to get data through dailup connection.

     

    any body help me how to get data using through dialup connection.

     

     

    Thanks and Regards,

    Ramaprasad.R


    0 0

    How to  identify what are records to go to replicate and what are rows are got replicated in Merge replication

    0 0

    What is impact on transactional replication if we disable the Xp_CmdShell?

    0 0

    Can someone provide me with a link or a list explaining to me the differences between Replication and a database mirror? I'm referring to SQL 2005. Thank you'll so much.


    0 0

    I have a transaction publication with over 8000 articles in it with a pull subscription.  After I create the new publication and then add the 8000 tables, I start the snapshot agent and it completes without errors.  I noticed that during the data load that serveral tables are missing on the subscriber.  I checked the snapshot repldata folder and also notices that these tables also do have a schema generated during the snapshot creation process.

    Can someone tell me why this is happening?


    0 0
  • 04/04/13--09:35: SQL 2000 Merge Replication
  • Hi

    As always I have a problem that is very frustrating.  We have used SQL 2000 (I know it's old) and have been looking to move to another version, but the test cycle is difficult because of the multi-site replication scenarios that we have in place.

    Anyway, we have a number of SQL 2000 servers (SP4) and all of a sudden I have problems with the merge replication.   So,

    1) I have removed the publication completely from the subscribers and the publisher. 

    2) Cleaned the database (at both the subsriber and publisher) for all signs of replication.

    3) Removed all of the tables used in the publication fro the subscriber.

    4) Rebuilt the replication using existing scripts.

    However I am getting the following error:

    The process could not enumerate changes at the 'Subscriber'.

    Which seems to come from the error - Numeric value out of range

    I have turned on debugging as can be seen below...

     

    Any help would be much appreciated...

    *****

    Debug

    *****

    Microsoft SQL Server Merge Agent 8.00.2066
    Copyright (c) 2000 Microsoft Corporation
    Microsoft SQL Server Replication Agent: SQL-UK2-DrivenWWUK-DrivenWWUK.Live.-SQL-UK-204

    Percent Complete: 0
    Connecting to Distributor 'SQL-UK2'
    Repl Agent Status: 3
    Connecting to Distributor 'SQL-UK2.'

    Server: SQL-UK2
    DBMS: Microsoft SQL Server
    Version: 08.00.2066
    user name: dbo
    API conformance: 2
    SQL conformance: 1
    transaction capable: 2
    read only: N
    identifier quote char: "
    non_nullable_columns: 1
    owner usage: 31
    max table name len: 128
    max column name len: 128
    need long data len: Y
    max columns in table: 1024
    max columns in index: 16
    max char literal len: 524288
    max statement len: 524288
    max row size: 524288

    [4/4/2013 5:13:48 PM]SQL-UK2.: {call sp_MSgetversion }
    [4/4/2013 5:13:48 PM]SQL-UK2.: {call sp_helpdistpublisher (N'SQL-UK2') }
    [4/4/2013 5:13:48 PM]SQL-UK2.distribution: select datasource, srvid from master..sysservers where upper(srvname) = upper(N'SQL-UK2')
    [4/4/2013 5:13:48 PM]SQL-UK2.distribution: select datasource, srvid from master..sysservers where upper(srvname) = upper(N'SQL-UK')
    [4/4/2013 5:13:48 PM]SQL-UK2.distribution: {call sp_MShelp_merge_agentid (0, N'DrivenWWUK', N'DrivenWWUK.Live.', 4, N'DrivenWWUKRep')}
    [4/4/2013 5:13:48 PM]SQL-UK2.distribution: {call sp_MShelp_profile (204, 4, N'')}
    Percent Complete: 0
    Connecting to Publisher 'SQL-UK2.DrivenWWUK'
    Initializing
    Repl Agent Status: 1

    Server: SQL-UK2
    DBMS: Microsoft SQL Server
    Version: 08.00.2066
    user name: dbo
    API conformance: 2
    SQL conformance: 1
    transaction capable: 2
    read only: N
    identifier quote char: "
    non_nullable_columns: 1
    owner usage: 31
    max table name len: 128
    max column name len: 128
    need long data len: Y
    max columns in table: 1024
    max columns in index: 16
    max char literal len: 524288
    max statement len: 524288
    max row size: 524288

    [4/4/2013 5:13:48 PM]SQL-UK2.DrivenWWUK: set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select collationproperty(@collation, N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle'
    Connecting to Publisher 'SQL-UK2.DrivenWWUK'
    Percent Complete: 1
    Connecting to Publisher 'SQL-UK2'
    Repl Agent Status: 3

    Server: SQL-UK2
    DBMS: Microsoft SQL Server
    Version: 08.00.2066
    user name: dbo
    API conformance: 2
    SQL conformance: 1
    transaction capable: 2
    read only: N
    identifier quote char: "
    non_nullable_columns: 1
    owner usage: 31
    max table name len: 128
    max column name len: 128
    need long data len: Y
    max columns in table: 1024
    max columns in index: 16
    max char literal len: 524288
    max statement len: 524288
    max row size: 524288

    [4/4/2013 5:13:48 PM]SQL-UK2.DrivenWWUK: {call sp_MSsetaccesslist (?, ?, ?)}
    [4/4/2013 5:13:48 PM]SQL-UK2.DrivenWWUK: {call sp_MSgetversion }
    [4/4/2013 5:13:48 PM]SQL-UK2.DrivenWWUK: {call sp_MSchecksnapshotstatus (N'DrivenWWUK.Live.')}
    [4/4/2013 5:13:48 PM]SQL-UK2.DrivenWWUK: {call sp_helpmergepublication (N'DrivenWWUK.Live.')}
    [4/4/2013 5:13:48 PM]SQL-UK2.DrivenWWUK: {call sp_MSgetreplicainfo(?,?,?,?,?,?,?)}
    [4/4/2013 5:13:48 PM]SQL-UK2.distribution: {call sp_MShelp_subscriber_info (N'SQL-UK2', N'SQL-UK')}
    Connecting to Subscriber 'SQL-UK.DrivenWWUKRep'

    Server: SQL-UK
    DBMS: Microsoft SQL Server
    Version: 08.00.2065
    user name: dbo
    API conformance: 2
    SQL conformance: 1
    transaction capable: 2
    read only: N
    identifier quote char: "
    non_nullable_columns: 1
    owner usage: 31
    max table name len: 128
    max column name len: 128
    need long data len: Y
    max columns in table: 1024
    max columns in index: 16
    max char literal len: 524288
    max statement len: 524288
    max row size: 524288

    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MSreplcheck_subscribe}
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MSgetversion }
    Percent Complete: 2
    [4/4/2013 5:13:48 PM]SQL-UK2.DrivenWWUK: {call sp_MSgetreplicainfo(?,?,?,?,?,?,?)}
    Connecting to Subscriber 'SQL-UK'
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MSgetreplicainfo(?,?,?,?,?,?,?)}
    Repl Agent Status: 3
    [4/4/2013 5:13:48 PM]SQL-UK2.DrivenWWUK: {call sp_MShelpmergearticles (?, 8000000, ?) }
    Percent Complete: 3
    Retrieving publication information
    Repl Agent Status: 3
    Percent Complete: 4
    Retrieving subscription information
    Repl Agent Status: 3
    [4/4/2013 5:13:48 PM]SQL-UK2.DrivenWWUK: {call sp_MSenumschemachange (?, ?, 8000500, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 210000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 3270000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 1170000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 49000000, 100000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 1600000, 100000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 400000, 100000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 300000, 100000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 13700000, 100000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 160000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 1800000, 100000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 1300000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 1020000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 110000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 3190000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 160000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 200000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 200000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 160000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 160000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 170800000, 100000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 40000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 5180000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 33400000, 100000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 74700000, 100000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 5190000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 5840000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 5160000, 10000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 300000, 100000, ?, ?) }
    [4/4/2013 5:13:48 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 4510000, 10000, ?, ?) }
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 1460000, 10000, ?, ?) }
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 30000, 10000, ?, ?) }
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MScheckidentityrange(?, ?, 4850000, 10000, ?, ?) }
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSgetreplicainfo(?,?,?,?,?,?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_MSsetreplicainfo (?,?,?,?,?,?,?,?,?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSgetreplicainfo(?,?,?,?,?,?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSmergeupdatelastsyncinfo (?,?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_mergemetadataretentioncleanup(?, ?, ?)}
    Percent Complete: 4
    The merge process is cleaning up meta data in database 'DrivenWWUK'.
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_mergemetadataretentioncleanup(?, ?, ?)}
    Repl Agent Status: 3
    Percent Complete: 4
    The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
    Repl Agent Status: 3
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSenumreplicas (?) }
    Percent Complete: 4
    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_MSenumreplicas (?) }
    The merge process is cleaning up meta data in database 'DrivenWWUKRep'.
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_helpmergealternatepublisher(N'SQL-UK2', N'DrivenWWUK', N'DrivenWWUK.Live.')}
    Repl Agent Status: 3
    Percent Complete: 4
    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_helpmergealternatepublisher(N'SQL-UK2', N'DrivenWWUK', N'DrivenWWUK.Live.')}
    The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSgetlastsentrecgens (?)}
    Repl Agent Status: 3
    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_MSgetlastsentrecgens (?)}
    Percent Complete: 4
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSgetmakegenerationapplock(?)}
    Uploading data changes to the Publisher
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSmakegeneration (?)}
    Repl Agent Status: 3
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSreleasemakegenerationapplock}
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSenumgenerations (75, ?, 1) }
    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_MScheckexistsgeneration (?, ?) }{call sp_MScheckexistsgeneration (?, ?) }{call sp_MScheckexistsgeneration (?, ?) }{call sp_MScheckexistsgeneration (?, ?) }{call sp_MScheckexistsgeneration (?, ?) }{call sp_MScheckexistsgeneration (?, ?) }{call sp_MScheckexistsgeneration (?, ?) }{call sp_MScheckexistsgeneration (?, ?) }{call sp_MScheckexistsgeneration (?, ?) }{call sp_MScheckexistsgeneration (?, ?) }{call sp_MScheckexistsgeneration (?, ?) }{call sp_MScheckexistsgeneration (?, ?) }{call sp_MScheckexistsgeneration (?, ?) }{call sp_MScheckexistsgeneration (?, ?) }{call sp_MScheckexistsgeneration (?, ?) }
    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_MSinsertgenhistory (?,?,?,?,?,?) }{call sp_MSinsertgenhistory (?,?,?,?,?,?) }{call sp_MSinsertgenhistory (?,?,?,?,?,?) }{call sp_MSinsertgenhistory (?,?,?,?,?,?) }{call sp_MSinsertgenhistory (?,?,?,?,?,?) }{call sp_MSinsertgenhistory (?,?,?,?,?,?) }
    Connecting to Subscriber 'SQL-UK.DrivenWWUKRep'

    Server: SQL-UK
    DBMS: Microsoft SQL Server
    Version: 08.00.2065
    user name: dbo
    API conformance: 2
    SQL conformance: 1
    transaction capable: 2
    read only: N
    identifier quote char: "
    non_nullable_columns: 1
    owner usage: 31
    max table name len: 128
    max column name len: 128
    need long data len: Y
    max columns in table: 1024
    max columns in index: 16
    max char literal len: 524288
    max statement len: 524288
    max row size: 524288

    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSgetversion }
    Connecting to Publisher 'SQL-UK2.DrivenWWUK'

    Server: SQL-UK2
    DBMS: Microsoft SQL Server
    Version: 08.00.2066
    user name: dbo
    API conformance: 2
    SQL conformance: 1
    transaction capable: 2
    read only: N
    identifier quote char: "
    non_nullable_columns: 1
    owner usage: 31
    max table name len: 128
    max column name len: 128
    need long data len: Y
    max columns in table: 1024
    max columns in index: 16
    max char literal len: 524288
    max statement len: 524288
    max row size: 524288

    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_MSgetversion }
    Connecting to Subscriber 'SQL-UK.DrivenWWUKRep'

    Server: SQL-UK
    DBMS: Microsoft SQL Server
    Version: 08.00.2065
    user name: dbo
    API conformance: 2
    SQL conformance: 1
    transaction capable: 2
    read only: N
    identifier quote char: "
    non_nullable_columns: 1
    owner usage: 31
    max table name len: 128
    max column name len: 128
    need long data len: Y
    max columns in table: 1024
    max columns in index: 16
    max char literal len: 524288
    max statement len: 524288
    max row size: 524288

    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSgetversion }
    Connecting to Publisher 'SQL-UK2.DrivenWWUK'

    Server: SQL-UK2
    DBMS: Microsoft SQL Server
    Version: 08.00.2066
    user name: dbo
    API conformance: 2
    SQL conformance: 1
    transaction capable: 2
    read only: N
    identifier quote char: "
    non_nullable_columns: 1
    owner usage: 31
    max table name len: 128
    max column name len: 128
    need long data len: Y
    max columns in table: 1024
    max columns in index: 16
    max char literal len: 524288
    max statement len: 524288
    max row size: 524288

    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_MSgetversion }
    Connecting to Subscriber 'SQL-UK.DrivenWWUKRep'

    Server: SQL-UK
    DBMS: Microsoft SQL Server
    Version: 08.00.2065
    user name: dbo
    API conformance: 2
    SQL conformance: 1
    transaction capable: 2
    read only: N
    identifier quote char: "
    non_nullable_columns: 1
    owner usage: 31
    max table name len: 128
    max column name len: 128
    need long data len: Y
    max columns in table: 1024
    max columns in index: 16
    max char literal len: 524288
    max statement len: 524288
    max row size: 524288

    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSgetversion }
    Connecting to Publisher 'SQL-UK2.DrivenWWUK'

    Server: SQL-UK2
    DBMS: Microsoft SQL Server
    Version: 08.00.2066
    user name: dbo
    API conformance: 2
    SQL conformance: 1
    transaction capable: 2
    read only: N
    identifier quote char: "
    non_nullable_columns: 1
    owner usage: 31
    max table name len: 128
    max column name len: 128
    need long data len: Y
    max columns in table: 1024
    max columns in index: 16
    max char literal len: 524288
    max statement len: 524288
    max row size: 524288

    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_MSgetversion }
    Connecting to Subscriber 'SQL-UK.DrivenWWUKRep'

    Server: SQL-UK
    DBMS: Microsoft SQL Server
    Version: 08.00.2065
    user name: dbo
    API conformance: 2
    SQL conformance: 1
    transaction capable: 2
    read only: N
    identifier quote char: "
    non_nullable_columns: 1
    owner usage: 31
    max table name len: 128
    max column name len: 128
    need long data len: Y
    max columns in table: 1024
    max columns in index: 16
    max char literal len: 524288
    max statement len: 524288
    max row size: 524288

    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSgetversion }
    Connecting to Publisher 'SQL-UK2.DrivenWWUK'

    Server: SQL-UK2
    DBMS: Microsoft SQL Server
    Version: 08.00.2066
    user name: dbo
    API conformance: 2
    SQL conformance: 1
    transaction capable: 2
    read only: N
    identifier quote char: "
    non_nullable_columns: 1
    owner usage: 31
    max table name len: 128
    max column name len: 128
    need long data len: Y
    max columns in table: 1024
    max columns in index: 16
    max char literal len: 524288
    max statement len: 524288
    max row size: 524288

    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_MSgetversion }
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSenumdeletesmetadata(?,?,?,?,?,?,0,?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_MSenumcolumns (?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSenumchanges(?,?,?,?,?,?,?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_MSenumcolumns (?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSenumchanges(?,?,?,?,?,?,?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_MSgetmetadatabatch(?,?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSenumdeletesmetadata(?,?,?,?,?,?,0,?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_MSenumcolumns (?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSenumchanges(?,?,?,?,?,?,?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_MSenumcolumns (?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSenumchanges(?,?,?,?,?,?,?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_MSgetmetadatabatch(?,?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSenumchanges(?,?,?,?,?,?,?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_MSenumcolumns (?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSenumchanges(?,?,?,?,?,?,?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK2.DrivenWWUK: {call sp_MSenumcolumns (?,?)}
    [4/4/2013 5:13:49 PM]SQL-UK.DrivenWWUKRep: {call sp_MSenumchanges(?,?,?,?,?,?,?,?)}
    The process could not enumerate changes at the 'Subscriber'.
    Percent Complete: 0
    The process could not enumerate changes at the 'Subscriber'.
    Repl Agent Status: 6
    Percent Complete: 0
    Category:NULL
    Source:  Merge Replication Provider
    Number:  -2147200999
    Message: The process could not enumerate changes at the 'Subscriber'.
    Repl Agent Status: 3
    Percent Complete: 0
    Category:SQLSERVER
    Source:  SQL-UK
    Number:  0
    Message: Numeric value out of range
    Repl Agent Status: 3
    Disconnecting from Subscriber 'SQL-UK'
    Disconnecting from Publisher 'SQL-UK2'
    Disconnecting from Subscriber 'SQL-UK'
    Disconnecting from Subscriber 'SQL-UK'
    Disconnecting from Subscriber 'SQL-UK'
    Disconnecting from Subscriber 'SQL-UK'
    Disconnecting from Publisher 'SQL-UK2'
    Disconnecting from Publisher 'SQL-UK2'
    Disconnecting from Publisher 'SQL-UK2'
    Disconnecting from Publisher 'SQL-UK2'
    Disconnecting from Publisher 'SQL-UK2'
    Disconnecting from Distributor 'SQL-UK2'


    0 0

    I wander if a tool (even with license fees) exists to be able to redo log or trap DML statements (Update, Insert, Delete).

    I would need to retrieve all the statements from a file that could be synchronized with another machine.

    For example I can start an audit with SQLProfiler and when I stop the audit, I can read DML staement without any information of data values.

    I would like to use a snapshot to restore the database and redo logs on this database for recovery purpose in case the primary machine crashes...

    I can easily do backup snapshot several times a day and would need to retrieve all statements (Update, Insert, Delete) since the last checkpoint (snapshot). These statements should be written in a file on the "mirroring" machine.

    I don't want indeed the mirroring feature from SQLserver as I could have only 2 machines without witness to manage the fail-over feature.

    Any comments would be appreciated.

    JNB


    0 0

    We encountered the following error when we tried to add a new table to replication 'Invalid date format...Error executing a batch of commands.  Retrying individual commands'.  After looking at the update statement replication was trying to execute, we noticed that a value for one of the date columns was '00-00-0000'.  On the Oracle table the value as 1/1/0001 so I'm assuming SQL cast it to '00-00-0000'.  We tried changing the data type in the subscriber table to nvarchar(19) and datetime2(7) as well as the update stored procedure but it did not work.  Any help will be appreciated.  Thanks.

    Tae


    tae yang


    0 0

    I have been 'playing' setting up merge replication just so i can get a feel for what is going on, now I want to clean everything out and start afresh but I cannot remove the distributor I deleted the subscription and publication Ok.

    I get

    Could not drop the Distributor 'DELLDUO'. This Distributor has associated distribution databases.

    and when I try to delete the database directly using drop  get

    Cannot drop the database 'MPCDistribution' because it is being used for replication.




    jnc

    0 0

    I need save replication delay  data to table.I run this sentence

    exec distribution.dbo.sp_replmonitorhelppublication @publisher = Myservername,
    @publisher_db =NULL,
    @publication_type = 0

    I got some data. I have to save query results to table.but I try all ways got failure.

    first one ,i try to used  nest procedure ,I got it next error information

    like this

    insert into @tmp
     exec distribution.dbo.sp_replmonitorhelppublication @publisher = Myservername,
    @publisher_db =NULL,
    @publication_type = 0

     An INSERT EXEC statement cannot be nested.

    second I used  sp_addlinkedserver @server = 'LOCALSERVER',  @srvproduct = '',
                       @provider = 'SQLOLEDB', @datasrc = @@servername
    I got next error information

    The OLE DB provider "SQLNCLI10" for linked server "LOCALSERVER" supplied inconsistent metadata for a column. The name was changed at execution time.

    I just want to save query data to other table.

    anyone can help me. thanks for you help.

    my os is windows  server 2008 64 bits .

    sql server version  is

    Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)   Apr  2 2010 15:48:46   Copyright (c) Microsoft Corporation  Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

     


    0 0

    Using Transactional replication.

    I would like to subscribe to a publication in order to transfer all the objects (tables, indexes, PKs) but not bring over the Snapshot of the data (saving tons of time).

    To that model I would then add all our non replicated objects (derived Tables, additional indexes, etc)

    I would then use that model as a means of comparing to an existing DB in order to ID any structural Diffs that need to be scripted.

    Someone mentioned not implementing the SPs for Insert/Update/Delete but I don't think that would prevent the initial Snapshot from being applied and that Snapshot has a ton of data.

    Is there any way to transfer the structure but not the Snapshot of the Data to a subscriber?

    Thanks

    ...Ray



    ...Ray


    0 0

    Hi,

    I have SQL server 2012 std. I received error:

    Could not load the DLL xprepl.dll, or one of the DLLs it references. Reason: (null).

    All the story:

    --------------

    Event ID 33090: Attempting to load library 'xprepl.dll' into memory. This is an informational message only. No user action is required.

    Event ID 33081: Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\xprepl.dll'.

    Error event ID: 17750: Could not load the DLL xprepl.dll, or one of the DLLs it references. Reason: (null).

    ------------

    I checked the folder "C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn" and file "xprepl.dll" is not there.

    What does this error mean and should I worry about it? thanks


    0 0

    hi my frnds....

    greetings.....!

    pls forward common issues in transactional replication ?

    this is my interviw quetion.

    Thanks in advance................

    Best regards..

    vijay


    0 0

    I was wandering if we could append to a file, with low latency (less than 5 seconds) DML statement to be able to redo logs after restoring a database from a previous backup.

    I'm working indeed on a small database and need to catch all DML statements: a maximum of 10 000 statements in one hour (30 tables).

    We've just find a way to write to a file all DML statements (from SQLServer2008R2 Express), as the profiler does (SQLServer Standard trace feature). Then parsing this file to prepare a SQL script could enable us to "redo logs" since last backUp.

    Hope this could work. Anyone has experienced with this kind of stuff?

    JNB



    0 0

    SQL Server 2005 SP4 with Transactional replication.

    I have this Database Log, which keeps growing due to a Pending transaction in the Database Log. (DB in SIMPLE recovery Mode)

    If i issue a DBCC OPENTRAN i get :

    Replicated Transaction Information:
     Oldest distributed LSN     : (0:0:0)
     Oldest non-distributed LSN : (47839439:351:1)

    The following Query using fn_dblog gives me LSN and Transaction ID Info.
    select * from::fn_dblog(NULL,'47839439:351:1') -Gives me this result

    If i have to Shrink the Log i have to use sp_repldone to mark the transactions as replicated or skipped.

    I take precautions in running this statement as this is not always what you want to do manually as it is internally done by the Log Reader Agent.

    EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0,     @time = 0,  @reset=1

    Now.. What if i Just want to mark just the transaction in question as done.. using the @xactid 

    How can i translate the CurrentLSN or TransactionID or LogRecord or Transaction SID or any other vlue to--> @xactid.....



    0 0

    Hello,

    I'm relatively new to setting up Transactional Replication and I've been running into a bit of a problem that I was hoping someone could help with.

    Essentially I have two different SQL instances with different names, but they contain databases that have the same name. One is a lab environment, the other a production environment. The production environment also has the ReportServer databases on it and already has transactional replication working on it (setup by my predecessor).

    With the above in mind I'm trying to setup the lab environment to also use transactional replication using a copy of the production database on it, but when I get as far as creating a publisher and start up the replication jobs some really weird stuff happens. For one, some of the replication jobs on the production server (which jobs appears to be random) stop working and say they can not execute'sp_replcmds' on the instance the production DB's reside. Further, when anyone tries to run a report on SSRS they get an error stating that the report server cannot open a connection to the report server database.

    If I delete the publication on the lab server and have the report server restarted, the issues go away. Replication starts working on the production sever again and people can access their reports.

    Has anyone seen this before? My gut feeling is this is some sort of permissions or naming issue, but for the life of me I can't see why actions taken on a lab server would impact an entirely different SQL instance on the production server.

    Thanks for any help.


older | 1 | .... | 37 | 38 | (Page 39) | 40 | 41 | .... | 181 | newer