Viewing 15 posts - 17,086 through 17,100 (of 59,067 total)
GilaMonster (8/7/2016)
Jeff Moden (8/7/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2016 at 1:48 pm
pedrolopezmail (8/7/2016)
Looks like using azure automation and a runbook is the prefer way for WindowAzure. You will need to know powershell to execute the SQL command. like invoke-sqlcmd.https://drive.google.com/open?id=0B0S1Vqb-7RcfelBBejdFMWxFYzQ
https://drive.google.com/open?id=0B0S1Vqb-7RcfWGhZUXRsekpUSjA
Heh......
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2016 at 10:31 am
TheSQLGuru (8/7/2016)
...more importantly they REALLY should be DOING proper statistics updates.
+ 1,000,000!
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2016 at 10:29 am
As a bit of a sidebar, unless you've made the mistake of shrinking your database, which causes the worst kind of fragmentation possible, fragmentation usually isn't what really costs you...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2016 at 10:26 am
p.s. SQL Server can't actually handle UTF-8 until you get to 2016.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2016 at 9:36 am
The "gibberish" in the data looks more like possible punctuation or special character marking. It looks like it may a "simple" code page problem.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2016 at 9:30 am
The Dixie Flatline (8/6/2016)
Eirikur Eiriksson (8/6/2016)
The Dixie Flatline (8/6/2016)
Answer withdrawn because I prefer not to answer interview questions.Just curious, how do you determine that this is an interview question?
😎
I don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2016 at 8:55 am
Adding memory will almost always help some but there's really only one way to fix this problem and everyone tries to avoid it with trickery that usually doesn't work. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2016 at 10:58 am
rajemessage 14195 (8/6/2016)
which one is good way of putting nolock
other think is
Omitting the WITH keyword is a deprecated feature: This feature will be removed in a future version of Microsoft...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2016 at 10:47 am
rajemessage 14195 (8/6/2016)
in sql server 2016 json has been introduced, i wanted to know
, should we change to jsaon and leave xml.
because we are keeping configuration in xml in...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2016 at 10:22 am
lmarkum (8/5/2016)
I did find 165 indexes that had the NO_RECOMPUTE option on the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2016 at 10:01 am
Understood. You missed the reason why I asked the question. I'll try to be more specific in the future.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2016 at 9:28 pm
TheSQLGuru (8/5/2016)
Jeff Moden (8/5/2016)
While this doesn't qualify as the proverbial "monster join" table, it may well be worth your while to divvy it up using "Divide'n'Conquer" methods that store an...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2016 at 8:29 pm
drew.allen (8/5/2016)
I'm getting frustrated. http://www.sqlservercentral.com/Forums/Topic1807080-391-1.aspxDrew
Edited to place the bold tags outside of the url.
The OP isn't bagging what you're raking. It may be time to break out the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2016 at 7:24 pm
Phil Parkin (8/5/2016)
Hugo Kornelis (8/5/2016)
drew.allen (8/5/2016)
I'm getting frustrated. http://www.sqlservercentral.com/Forums/Topic1807080-391-1.aspxDrew
Edited to place the bold tags outside of the url.
Interesting topic. Thanks, Drew - I weighed in with my two cents...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2016 at 7:21 pm
Viewing 15 posts - 17,086 through 17,100 (of 59,067 total)