Twitter | Search | |
Robert L Davis
Database Engineer at BlueMountain Capital Management............. Certified Master: SQL Server... MVP... Poker player... Ordained Pastafarian... Native American
90,543
Tweets
687
Following
6,557
Followers
Tweets
Robert L Davis 37m
Replying to @sqL_handLe
I would love for there to be an option to set to favor redo or user queries.
Reply Retweet Like
Robert L Davis retweeted
Seattle Seahawks 1h
It's the FINAL day to . 💪 Flex that RT button to help your earn Pro Bowl honors.
Reply Retweet Like
Robert L Davis 1h
Replying to @SQLHA @PearlKnows
And of course depends on the size and number of the databases as backup/restore is required at some level.
Reply Retweet Like
Robert L Davis 1h
Replying to @sqL_handLe
Why are you trying to control which CPUs redo runs on?
Reply Retweet Like
Robert L Davis 1h
Replying to @sqL_handLe
Redo doesn't consume threads unless there is work to do so I don't see how that would work.
Reply Retweet Like
Robert L Davis retweeted
Look Park 2h
The 265 members of Congress who sold you out to ISPs, and how much it cost to buy them
Reply Retweet Like
Robert L Davis 2h
Replying to @ukgav
You'd think someone would have a repository. Never found one.
Reply Retweet Like
Robert L Davis 2h
Replying to @sqL_handLe
Couldn't be less predictable.
Reply Retweet Like
Robert L Davis 4h
Replying to @markvsql
So am I. :)
Reply Retweet Like
Robert L Davis 5h
You just proved my point.
Reply Retweet Like
Robert L Davis 7h
Education is only bad if it's not parochial.
Reply Retweet Like
Robert L Davis retweeted
Michael W Lucas, pulp tech author 7h
I know what trickles down from the rich. It ain't money.
Reply Retweet Like
Robert L Davis 7h
Come to SQLSaturday Victoria before the MVP Summit and we can get some poutine together.
Reply Retweet Like
Robert L Davis 7h
Slack is going to kill email. Also, NoSQL is going to kill SQL Server, Azure is going to kill the DBA role, and poutine is going to kill plain french fries.
Reply Retweet Like
Robert L Davis 7h
Replying to @YaHoznaDBA
I wonder if it's a difference in our permissions level or something they do purposefully or a bug.
Reply Retweet Like
Robert L Davis 7h
Replying to @YaHoznaDBA
Well, they are tables and procedures so you should still be able to manually drop them.
Reply Retweet Like
Robert L Davis 8h
Replying to @YaHoznaDBA
Can you configure replication and then drop it and disable it? Sometimes that works.
Reply Retweet Like
Robert L Davis 8h
Replying to @underwaterryan
But I'm doubtful that will work.
Reply Retweet Like
Robert L Davis 8h
Replying to @underwaterryan
You can try creating a plan guide and adding the forceseek hint to it.
Reply Retweet Like
Robert L Davis 8h
Replying to @YaHoznaDBA
If they didn't get removed by dropping replication, run sp_removedbreplication.
Reply Retweet Like