Viewing 15 posts - 17,116 through 17,130 (of 59,101 total)
VastSQL (8/7/2016)
You can script out all jobs at once by listing the jobs in object explorer details-->select all jobs--> right click -->script jobs
+1.
For those that don't know how to get...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2016 at 2:17 pm
mikes84 (8/7/2016)
That's some interesting insight. I don't think I would have necessarily thought updating one was more important than updating the other. I'll make sure to ensure statistics get updated...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2016 at 2:11 pm
pietlinden (8/7/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2016 at 2:02 pm
To repeat what I stated on the following forum for this exact same question...
http://forums.sqlteam.com/t/t-sql-2012-trigger-and-generate-email-message/7349/2
Wouldn't it be easier to just prevent the duplicate "record" to begin with?
Apparently SQLTeam.Jassie1 = SSC.Wendy Elizabeth.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2016 at 1:59 pm
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
Viewing 15 posts - 17,116 through 17,130 (of 59,101 total)