Forum Replies Created

Viewing 15 posts - 1,921 through 1,935 (of 3,616 total)

  • RE: Time Bomb Design - A Longer Fuse

    My thanks to Paul for his help in resolving the SQL2005 conundrum.

    It was my bad. SQL2005 does reclaim space when the clustered index is rebuilt.

    SQL2000 doesn't and this I...

  • RE: Time Bomb Design - A Longer Fuse

    lastory2006 (5/26/2010)


    BTW - in the half-page/full-page example - just use varchar and be done with it, while at the same time taking up minimal storage space.

    The point of the...

  • RE: Time Bomb Design - A Longer Fuse

    @sipe_16

    When you use an ORM tool it effectively hides the schema so you can get away with calling the fields almost anything.

    When you are reading down a large block of...

  • RE: Time Bomb Design - A Longer Fuse

    Paul White NZ (5/26/2010)


    This is not so.

    Rebuilding the clustered index does indeed reclaim the space.

    What am I doing wrong Paul? I don't seem to get any space...

  • RE: Five Things to Trim From SQL Server

    I want to make it totally impossible to use a SQL reserved word or T-SQL extension as an object name.

    Being able to wrap up a reserved word in square brackets...

  • RE: Scaling Out the Distribution Database

    I noticed the extended property when I worked through management studio and the script is for when I don't want to use management studio.

    for real deployments everything has to be...

  • RE: Company Rewards

    A thank-you would be nice.

    A personal training budget would be fantastic especially if I actually got to use what I learnt on the course.

    I've just attended SQLBits 6 in London...

  • RE: Scaling Out the Distribution Database

    Just curious - have you looking into replicating stored procedure execution to cut down on the transaction volume?

    Absolutely, I was intending to write up an article on it. It...

  • RE: Scaling Out the Distribution Database

    Paul White NZ (3/31/2010)


    Assuming the box is licenced per-processor, would you expect any advantage to running the separate distribution databases in separate instances?

    I'm not up to date with licensing requirements...

  • RE: Scaling Out the Distribution Database

    Varies from

    Physical 8CPU 64bit W2K8 SQL2008 standard edition with 12GB RAM to

    Virtual 4CPU 32bit W2K3 SQL2005 Standard edition with 8 GB RAM.

    Mainly push subscriptions but pull used for...

  • RE: Scaling Out the Distribution Database

    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 billion...

  • RE: Scaling Out the Distribution Database

    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.

    Try reindexing a very large...

  • RE: Scaling Out the Distribution Database

    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 and...

  • RE: Scaling Out the Distribution Database

    It is very hard to say what "a certain size" is because it depends on the hardware and configuration of the machine that is acting as a distributor and also...

  • RE: updating 1,000 records takes 5-6 minutes I would like to decrease the time that takes

    And I thought I was hard done by because a 1.5 million record update took 15 seconds!

Viewing 15 posts - 1,921 through 1,935 (of 3,616 total)