Results 1 to 4 of 4

Thread: Ad hoc queries..splitting tables using OUTPUT

  1. #1
    Join Date
    Feb 2009
    Posts
    3

    Ad hoc queries..splitting tables using OUTPUT

    I read your article on using OUTPUT and was wondering if it could help my situation.

    http://www.databasejournal.com/featu...PUT-Clause.htm


    I have 16 column table that gets 1000 inserts per second.

    I have developers that need to run ad-hoc queries on this table. "Select * from logger where user = 'dcp'"

    Problem is it take too long for these queries to come back.

    What if I were to implement what you did with OUTPUT and split the one table into two tables? Then the devs could query the second/new/'History' table without the blocking from all the inserts?

    Or is the impact the same because there are now two tables instead of one? Is there still a good chance I would get blocking on that second/history table?

  2. #2
    Join Date
    Sep 2002
    Posts
    5,938
    Are you in sql2k5 or sql2k8? Take look at snapshot isolation if so, it may address your issue.

  3. #3
    Join Date
    Feb 2009
    Posts
    3
    2k5.......

  4. #4
    Join Date
    Sep 2002
    Location
    Fantasy
    Posts
    4,254
    1. try database snapshot
    2. try replicating the database to another server and use that server dedicated for Ad-Hoc queries.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •