-
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?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|