Reputation
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
17 70
Newest
 Revival
Impact
~303k people reached

Jul
22
comment SQL server Index rebuild and restore not working
And start with Gail Shaw's excellent post, My Database is Corrupt, Now What: sqlservercentral.com/articles/Corruption/65804
Jul
21
comment Major Discrepancy Between SQLIO IOPS/Throughput Stats and DBCC CHECKDB Operations
Ah, typically I see people doing this in their development, QA, or staging environments as part of a data refresh, so there's no licensing incurred.
Jul
17
comment Security implications of restoring a backup from an unknown source?
@RemusRusanu launch the rockets on Moscow, hahaha, nice!
Jul
17
comment Is it possible for SQL Server to miss rows on a select * where PK = “value” query
@spence - right, but what about the isolation level of the connection? Using read uncommitted isolation means the exact same thing as putting nolock on the query.
Jul
16
comment Is it possible for SQL Server to miss rows on a select * where PK = “value” query
Actually, have you seen Kendra's demo of the combination of index intersection and dirty reads? She demos a scenario where the data returned in the query looks like it violates constraints, but it's because the two index reads were done at different times. It's really slick - email her if you want more details on it. (It wouldn't happen in Spence's problem since he took out the nonclustered indexes, of course.)
Jul
16
answered Security implications of restoring a backup from an unknown source?
Jul
16
comment Is it possible for SQL Server to miss rows on a select * where PK = “value” query
Right, but think about a transaction that does a delete (or moves the PK values, whatever) and then rolls it back while the select is running.
Jul
16
comment Is it possible for SQL Server to miss rows on a select * where PK = “value” query
The claims part is what's tough - if someone even just had a lock on a page, this can happen. I can conceive scenarios where someone takes a lock and doesn't change data, but it's skipped due to that isolation level.
Jul
16
comment Database/Storage engine suggestion for a project involving heavy inserts?
That's just a regular part of your backup and restore process. With SQL Server it's called log shipping, and I assume similar techniques are available for MySQL. You don't export the data - you just take a backup.
Jul
16
answered Is it possible for SQL Server to miss rows on a select * where PK = “value” query
Jul
16
answered Why is there ASYNC_NETWORK_IO wait type on Shared Memory connections?
Jul
16
comment Database/Storage engine suggestion for a project involving heavy inserts?
Data warehousing, yes - but that's the reporting side of it, not the data-insert side. Reading usually calls for different data structures than writing. Your question focused on the inserts. Put the reporting summary tables in a separate database (data warehouses are usually different from the heavily-inserted source data). Those are updated only once per day (or hourly, whatever) with batch jobs.
Jul
16
answered Object Auditing with Availability Groups
Jul
16
answered Replicating 3000+ SQL Server databases
Jul
16
answered Why are queries causing spill to tempdb?
Jul
16
comment Database/Storage engine suggestion for a project involving heavy inserts?
I don't work with MySQL, so I wouldn't be equipped to answer that one. You're best off clearly defining the table and the access styles, and then asking that as a separate question. That way you can tag the question with just the tags relevant to the question, and get better attention. DO NOT MAKE MONTHLY TABLES WITH DAYS AS FIELDS. Bad bad bad idea. Grab a book on database normalization quick. In the SQL Server world, I like Louis Davidson's Pro SQL Server 2012 Relational Database Design and Implementation.
Jul
16
answered Query to find optimal filegroups for objects
Jul
16
answered Major Discrepancy Between SQLIO IOPS/Throughput Stats and DBCC CHECKDB Operations
Jul
16
comment How to get output from trigger on linked server
Putting logging in the trigger is the way to go here, but the danger is setting up a big distributed transaction where the insert fires, plus the output table is read, all from a transaction done across servers. Recipe for concurrency problems there.
Jul
16
answered Database/Storage engine suggestion for a project involving heavy inserts?