Viewing 15 posts - 47,236 through 47,250 (of 59,095 total)
Dooza (11/14/2008)
Invalid object name 'Master.dbo.SysColumns'.
I think my master database is screwed 🙁
We did have some problems a few weeks back with a maintenance...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 11:43 am
Loner (11/14/2008)
Don't even get me started with outsourcing. In my last company, I spent 4 days to finish a very complicated report. The outsourcing company had two...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 11:33 am
AndrewMurphy (11/14/2008)
"Um... for what? Using a paltry 40 MB of TempDB?"
...if you read the original message...he was getting TEMPDB full....the only reason TEMPDB was being returned to 40MB was...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 11:29 am
You bet... thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 11:26 am
rosh (11/14/2008)
"Student","Subject", "Pass" , "Fail"....Looks like a homework question.....
Heh... and a "classic" homework question at that... that's why I asked "what have you tried so far". When people don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 11:21 am
Sure... you want all the rows of Summary Van No. to be the same?
Whichever, can you make it easy on me by providing the CREATE TABLE statement and some code...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 11:18 am
K. Brian Kelley (11/14/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 11:12 am
MikeM7 (11/14/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 10:57 am
Try the following...
SELECT COUNT(*) FROM Master.dbo.SysColumns
If it doesn't work, there are one of two problems... either you don't have the privs to read from the master database (very unusual) or...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 10:44 am
upperbognor,
Would you also post the code for the dbo.fn_patindexEnd function? Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 10:21 am
Dooza... what version of SQL Server are you using? Also, just to be absolutely clear, would you post the exact code that you're using so I can try to...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 10:15 am
I'll take a look, Dooza...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 10:10 am
Oh yeah... almost forgot... the reason why the WHERE clause actually works is because of my friend, the NULL value. It's not comparable using most relational operators unless someone...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 10:06 am
I thought I'd throw my 2 cents in here... both Seth and Chris did a cool job on this. But, being ever vigilant for every micro-second of performance, I've...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 9:53 am
Heh... no problem. I hate typing the code off the top of my head so I keep the script handy at all times.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2008 at 9:41 am
Viewing 15 posts - 47,236 through 47,250 (of 59,095 total)