Forum Replies Created

Viewing 15 posts - 16 through 30 (of 195 total)

  • RE: Make a 100+ Server Inventory in 30 minutes

    Great tip to get a quick inventory!

    I wrote a similar blog post about using a free tool called SYDI that uses WMI to gather system information and query\persist it in...

  • RE: Scaling Out the Distribution Database

    That said we are seeing a massive boost from running SQL2008 64 bit on W2K8.

    I'm guessing that's in part dueto the rewritten network stack in Windows 2008. There's a great...

  • RE: Scaling Out the Distribution Database

    David.Poole (3/31/2010)


    No offence taken.

    We have four production distributors two of which are virtual servers.

    We put roughly 24 billion transactions through them each day. We have spiked up to 370...

  • RE: Scaling Out the Distribution Database

    John.Sansom (3/31/2010)


    Kendal/David,

    Could you also post your CPU configurations please and whether or not you are using Push or Pull subscriptions.

    As I'm sure you know, Push subscriptions place more burden on...

  • RE: Scaling Out the Distribution Database

    David.Poole (3/30/2010)


    If you have everything hammering through one database you are talking about one transaction table having to deal with all transactions. Ditto the commands table.

    But if you have...

  • RE: Scaling Out the Distribution Database

    For example, let’s say we have two Publications that form part of an application platform. One Publication is sourced from a very intensive OLTP database and another Publication has relatively...

  • RE: Scaling Out the Distribution Database

    David.Poole (3/30/2010)


    On one particular publication we changed the retention period to 3 hours because if something goes wrong with the subscriber then the transactions start building up in the distributor...

  • RE: Scaling Out the Distribution Database

    RML51, the transaction retention period is used by the distribution cleanup agent to mark subscriptions as inactive if they are further behind than the retention period and to remove transactions...

  • RE: Scaling Out the Distribution Database

    I probably asked the question poorly, so let me take another approach...let's say I've been tasked with managing a replication environment and I notice that things are starting to get...

  • RE: Scaling Out the Distribution Database

    David,

    Can you elaborate on the following statement you made:

    the number of records in the MSRepl_transactions table is likely to be very high and once it has gone beyond a certain...

  • RE: Randomizing Result Sets with NEWID

    Using NEWID to do a random sort or grab a random number of rows from a result set is a HUGE performance killer and does not scale well. I've had...

  • RE: Log shipping vs Replication

    Based on your requirements it sounds like log shipping is more applicable, however keep in mind you'll need to change the recovery model on your database to support log shipping....

  • RE: Snap Shot error

    SQL New New (7/24/2009)


    It's happening on the publisher on the snap shot agent, it starts to bcp my articals then it fails with this error. I have 127GB on the...

  • RE: Replication latency troubleshooting

    Saurabh Aggarwal (7/24/2009)


    Replication latency troubleshooting:-

    In my enviornment we have created a multiple publications on each table level in a database...

    means each table will have single publication and these are really...

  • RE: Replication latency troubleshooting

    Have you looked at replication monitor? That should show you all of the information that you're looking for.

Viewing 15 posts - 16 through 30 (of 195 total)