Viewing 15 posts - 42,721 through 42,735 (of 59,102 total)
Lynn Pettis (7/29/2009)
Is this...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 29, 2009 at 9:32 pm
jason (7/29/2009)
b) have a dynamic, changing number of fields depending on the source data
See the following... http://www.sqlservercentral.com/articles/cross+tab/65048/
--Jeff Moden
Change is inevitable... Change for the better is not.
July 29, 2009 at 4:35 pm
bhavesh_183 (7/29/2009)
Finally I got it .... Thanks every oneBhavesh
Got what? Please share your solution.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 29, 2009 at 4:31 pm
ALZDBA (7/29/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 29, 2009 at 4:24 pm
I don't know why cursors where actually added to SQL back in version 6.5, but you can bet it was some market pressure by those who don't know how to...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 29, 2009 at 4:09 pm
Thanks, Paul... I tried the reinstall of the update. No joy. Fortunately, this isn't a production system and I've really not lost anything important. Guess I'll just...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 29, 2009 at 7:15 am
Steve Jones - Editor (7/28/2009)
How about advanced pork chop aiming strategies for maximum developer damage?
Heh... that's actually just the intermediate course. The advanced course is "How to teach pigs...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2009 at 9:56 pm
You need to add a table alias to #MainTemp and all columns cited in the WHERE clause so we can tell if you've made an accidental cross-join or not. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2009 at 12:12 pm
a2zwd (7/27/2009)
I was given a job to design the database for my application.
What is the procedure to design the database.
I mean the tools, database design life cycle, any...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2009 at 12:06 pm
Yeah.... just not one you release to the customer. You only have one chance to make a first impression. Unless the customer is fully aware that you're going...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2009 at 11:13 am
Sorry... the double post was my fault... trying to spin too many dishes at one time.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2009 at 11:05 am
Just testing for smileys in the "pre" code...
SELECT 1; SELECT (1); SELECT ( 1 ) SELECT ( 1 ); SELECT ( 1 ) ; ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2009 at 11:04 am
Just testing for smileys in the "pre" code...
SELECT 1; SELECT (1); SELECT ( 1 ) SELECT ( 1 ); SELECT ( 1 ) ; ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2009 at 11:02 am
Just testing for smileys in the "pre" code...
SELECT 1; SELECT (1); SELECT ( 1 ) SELECT ( 1 ); SELECT ( 1 ) ; ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2009 at 10:59 am
BTW, thanks for fixing the post for me. You can just bet I'll be using the "pre" code until you good folks have a chance to wittle on the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 28, 2009 at 10:52 am
Viewing 15 posts - 42,721 through 42,735 (of 59,102 total)