1,891 reputation
321
bio website movingsql.com
location New Jersey
age 56
visits member for 2 years, 6 months
seen 23 hours ago
coder & programmer of many defunct languages...

Oct
11
comment Disk usage spikes: good, bad or indifferent?
This is normal. Almost every SQL Server I've worked on that did not have serious problems looked like this. I'm pretty sure that this is checkpointing as @TomTom says.
Oct
11
asked What is Required to use Oracle Performance Manager to monitor SQL Server?
Oct
6
revised How to DROP multiple tables from databases?
corrected "delete" to "drop"
Oct
6
suggested suggested edit on How to DROP multiple tables from databases?
Oct
1
comment If a transaction is “committed” , is it then saved for sure?
@Giosco: It cannot. "committed" means that it is in the database's log file. The only way to lose it after that is to either 1) lose the log file before it is also saved to the data file, or 2) lose both the log file and the data file, or 3) human error. Note that (3) is usually the likeliest.
Sep
19
comment Dynamic Joining Across Databases
Unless the number of different possible databases is small, Dynamic SQL is probably your best bet.
Sep
18
answered How to know the user doing a delete action on an audit table, when using a shared login?
Sep
18
comment How to know the user doing a delete action on an audit table, when using a shared login?
Fair enough, I should have read your question more thoroughly. I think I have an answer for this, but I may not be able to post it until late tonight.
Sep
9
comment Plan cache memory: parameterized SQL vs stored procedures
The number one reason that I prefer stored procedures is their security control and options that are far superior to any other approach that I know of with SQL Server.
Jul
13
comment Check existence with EXISTS outperform COUNT! … Not?
Heh, you know, I have t-shirt with my username on it, but the first four letters crossed out ("<strike>RBAR</strike>RYYOUNG").
Jul
9
comment TempDB Version Store cleanup
"One of the applications hosted on the database instance has an open transaction that is 40 days old.." This cannot be doing your backups any favors either. Seriously, the best fix here is to stop doing that. Any program or product that holds a transaction open for such extended periods is very broken.
Jun
26
revised Finding the last command issued by a blocking process
added 2 characters in body
Jun
21
answered Finding the last command issued by a blocking process
Jun
6
awarded  Nice Answer
Jun
2
revised How to see what is cached in memory in SQL server 2008?
Add link author's last name.
Jun
2
suggested suggested edit on How to see what is cached in memory in SQL server 2008?
May
29
awarded  Nice Answer
May
20
comment Best practices with large amount of data
OK, fair enough.
May
20
comment Best practices with large amount of data
You present Normalization and Performance as co-equal and independent things in database design. They are neither. The first step in good design is always Normalization, because that's how you make sure that it's a correct design. Not coincidentally, the first step in Performance is also a normalized design. The number of tables has nothing material to do with either of these until much later in the process. Worrying about the number of tables during the design process is a recipe for bad designs, especially for someone who is unsure of what they are doing.
May
20
comment Best practices with large amount of data
"more tables is usually better.." is a gross oversimplification that easily leads beginners to create horribly non-relational designs (like the second one the OP proposed). Let them figure out Normalization first. Only when they understand that completely should they start to worry about the performance of the design (as opposed to the performance of the implementation, which is a different thing).