Reputation
889
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
7 17
Impact
~36k people reached

Feb
4
awarded  Notable Question
Feb
1
awarded  Notable Question
Jan
28
awarded  Popular Question
Jan
27
awarded  Yearling
Jan
19
comment SQL Server Log Shipping: File copy options?
This is not the log shipping of my dreams, but it is close! We are getting a lot closer to using azure , with the new file share function of azure. Then we can use encrypted backups and log backups, pushed to azure via robocopy, then pulled form azure with robocopy, and use your script to apply them.
Jan
19
accepted SQL Server Log Shipping: File copy options?
Jan
19
revised SQL Server Log Shipping: File copy options?
expand the thinking
Dec
30
revised SQL Server Log Shipping: Copy copies 0 files
added 322 characters in body
Dec
8
comment SQL Server: Programatically trigger export of db schema
Take 2: Totally cool w SMO, but is there a magic SMO func that does this, or an example to get us started?
Dec
8
asked SQL Server: Programatically trigger export of db schema
Sep
19
revised Easy replication for SQL Server: Can it be set up like mongodb or Oracle?
added 326 characters in body
Sep
18
revised Easy replication for SQL Server: Can it be set up like mongodb or Oracle?
updated the question for 2015... and current SQL versions
Sep
18
comment Easy replication for SQL Server: Can it be set up like mongodb or Oracle?
And now.... mirroring is deprecated.... and avail groups are humongous, complex pita to set up... and log shipping requires smb/ntfs across WAN... So now what?
Sep
18
accepted SQL Server 2005: Job scheduled every 4 hrs, but sp_help_jobactivity shows unexpected value for next_scheduled_run_date
Sep
18
accepted Launching a python script from an insert trigger
Sep
18
accepted How do I ensure only one instance of a job is running?
Sep
18
asked How do I ensure only one instance of a job is running?
Sep
18
comment sql server: updating fields on huge table in small chunks: how to get progress/status?
We are happy with 8 million rows/hour. Yes, we can see it slowing down. We are hesitant to create any more indexes (because the table is locked for the whole build). What we have done a couple of times is do a reorg on the existing index (because that is on line).
Sep
17
comment sql server: updating fields on huge table in small chunks: how to get progress/status?
Without the UPDATE enhancements, we are getting about 8 million updates/hour... with the @BatchRows set to 10000000 (ten million)
Sep
17
comment Large rolling update on huge table: Getting slower and slower
@Dave Nay, we are on standard edition.... no partitioning for us...