Viewing 15 posts - 27,316 through 27,330 (of 59,101 total)
Yes. SQL Server occasionally loses it's mind on such things. Over the last 16 years of using SQL Server, I've given up on trying to find the reasons....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 4, 2013 at 4:43 pm
On that note, get into SSMS and press the {f1} key. Select the index mode. Type "sys.dm" in the index box and start reading. There's not much...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 4, 2013 at 4:35 pm
Yelena Varshal (10/1/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 4, 2013 at 4:31 pm
Charmer (3/15/2012)
SQLKnowItAll (3/15/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 4, 2013 at 4:28 pm
I hardly ever use the word "stupid" in describing something but the people asking you to do this are freakin' stupid to their core! How many lawsuits do they...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 4, 2013 at 4:19 pm
tshad (3/4/2013)
That was what I thought, but wasn't sure.Thanks,
Tom
At this point, I recommend you press the {f1} key when you're in SSMS and use the "index" to find information about...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 4, 2013 at 4:03 pm
GregoryF (3/4/2013)
Evil Kraig F (3/4/2013)
GregoryF (3/4/2013)
Is it possible to pass a variable for MAXDop as a query hint?
As mentioned above... no.
However, why would you want to do this? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 4, 2013 at 4:00 pm
dhananjay.nagarkar (3/4/2013)
Thanks so much that worked as per requirement 🙂
Just make sure you don't actually store formatted dates. It WILL come back to bite you in a major way!
--Jeff Moden
Change is inevitable... Change for the better is not.
March 4, 2013 at 3:57 pm
Don't use the insert command as you currently have it. Contrary to popular belief, having the database in the SIMPLE recovery mode does NOT prevent the log file from...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 4, 2013 at 3:53 pm
Erin Ramsay (3/4/2013)
Booyah, Lowell! You hit it. I forgot to define the size of my stored proc variables.Good catch!
IIRC, that maximum size for a DOS Path is 512 bytes. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 4, 2013 at 3:28 pm
Wow! Awesome article, Geoff! This is spooky stuff. I knew that passwords mostly kept the honest man honest because there's lots of ways to crack them especially...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 4, 2013 at 8:10 am
alan_lynch (3/3/2013)
unknown.x in it even the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2013 at 9:23 pm
In the first query, you give SQL Server no choice. You say to find the MAX unconditionally for the given criteria and there isn't one so it returns a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2013 at 8:33 pm
Heh... dang it. Roshan Joe beat me to it. You can, however, make it one notch simpler. Not sure which will be faster, though.
UPDATE dbo.BigTable
...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2013 at 8:24 pm
Maybe, but I'd have done it a different way. The original data already has more than 1 level.
The original data also has a flaw in it that makes it...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2013 at 5:25 pm
Viewing 15 posts - 27,316 through 27,330 (of 59,101 total)