261 reputation
26
bio website 12titans.net/p/default.aspx
location New Zealand
age
visits member for 2 years, 10 months
seen Sep 26 '12 at 11:02

Sep
24
awarded  Autobiographer
Jul
13
awarded  Notable Question
Dec
16
awarded  Yearling
Nov
20
awarded  Popular Question
Feb
23
revised What are the top 3 performance Issues that you encounter with your SQL Servers?
added 224 characters in body
Feb
23
awarded  Student
Feb
23
comment How to revive SQL Server 2008R2 performance counters?
Yes, VS 11. The problem with the question on serverfault is that none of the posted answers resolved the issue. I'm hoping DBA-oriented users might be able to provide more useful help.
Feb
23
awarded  Editor
Feb
23
revised Fix missing performance counters
deleted 4 characters in body
Feb
23
asked Fix missing performance counters
Feb
23
answered What are the top 3 performance Issues that you encounter with your SQL Servers?
Feb
21
answered SQL: What is slowing down INSERTs if not CPU or IO?
Feb
18
comment What should I use as a primary key/index for a table with no unique columns that are mostly written to?
That's a good topic for another question, but briefly: if the source table can be large, you may want to enable BULK_LOGGED while you move the data over. Assuming the two tables have the same columns, then you can do something like DELETE FROM SrcTable OUTPUT DELETED.* INTO DestTable
Feb
18
comment What should I use as a primary key/index for a table with no unique columns that are mostly written to?
So, it sounds like you need to make a trade-off: extra cost at insert time vs. extra cost at query time vs. implementation complexity. Depending on your architecture, if you have times of day when the DB isn't busy, you might be able to offload it into a second table with a fulltext index, or perhaps even to an Analysis Services cube.
Feb
18
answered What should I use as a primary key/index for a table with no unique columns that are mostly written to?
Jan
3
comment sql server 2008 - controlling size of log file
right before the commands that are likely to fill up the log (update, insert or delete many rows or make schema changes). How do you know which ones those are? Your guess is as good as mine.
Jan
3
answered sql server 2008 - controlling size of log file
Dec
17
awarded  Teacher
Dec
17
answered Why so many logical reads?
Dec
17
answered Default SQL Server 2008 locking behaviour