Viewing 15 posts - 47,836 through 47,850 (of 59,099 total)
Heh... the point is that Interviewer's ask some of the darnedest questions to find out if you really know instead of just memorizing a list of "interview questions". 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 9:23 pm
chintan kotwal (10/9/2008)
I was reading an article, and in that article as one of the rules for the database architect being 'Every table has a Primary Key'.
My question: Would...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 8:53 pm
Heh... I agree... this is what cursors are for...
...but then you'd have to admit to actually putting one in production. 😛
In SQL Server 2005, there is absolutely no reason to...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 8:44 pm
bharathi (10/9/2008)
I found it myself...Thankss a lot anywayz...
Two way street here... would you please post your solution? Thanks. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 8:21 pm
Sure you can do it. And, you don't have to write a lick of T-SQL to do it... Enterprise Manager will write all of the code for you.
Open Enterprise...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 8:15 pm
Ummm... cramming for an interview is a bad thing. If you don't know an answer for a question they ask, chances are you really don't know and reciting a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 7:49 pm
maynor_ramirez (10/9/2008)
I need to pivot on some not all rows, I have search the sqlservercentral site for the answer but nothing yet..Thanks
[url="Cross Tabs and Pivots, Part 1 – Converting Rows...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 7:35 pm
That would grab /*__*/ if it's on the same line as some code of embedded within a statement.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 7:28 pm
Vincent Central (10/9/2008)
Thank you all for your replies. I have "coached" the offending developers and...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 6:47 pm
cdex3 (10/9/2008)
Thanks for the info!This is my first post so I apologize for any lack of etiquette.
Your never too old or too young to learn new things and ideas.
Heh......
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 6:17 pm
Oh yeah... almost forgot... you can usually get away without using an Index "Hint", but like ORDER BY in a Select, it's always best to have one to force the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 6:04 pm
That and you need a "anchor" column even if it doesn't do anything for the code... one that is just @variable = @column. Sometimes it works without one... don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 6:01 pm
rbarryyoung (10/9/2008)
Select *
From Locations
Where NOT EXISTS( Select * From Excludes
Where Location LIKE '%'+Excludes+'%')
This is probably close to what Jeff intended to write,...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 5:58 pm
Sergiy (10/9/2008)
Jeff Moden (10/9/2008)
change all the delimiters to a "thorn" and go for it.
There is no guarantee "thorn" is not or will not be used within the filed for...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 5:56 pm
Heh... I was hoping you had an IDENTITY PK... I won't have to make many changes to the script I just wrote above...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 5:54 pm
Viewing 15 posts - 47,836 through 47,850 (of 59,099 total)