Viewing 15 posts - 36,361 through 36,375 (of 59,067 total)
CELKO (10/13/2010)
....
Should have been:
UPDATE Foobar
SET ..
WHERE Foobar.id = @id
...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 13, 2010 at 6:10 pm
Steve Jones - SSC Editor (10/12/2010)
jcrawf02 (10/12/2010)
At the risk of encountering a porcine missile, have you ever heard of earplugs? 😀
I have found that single rooms are the best earplugs...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2010 at 5:27 pm
jcrawf02 (10/12/2010)
Jeff Moden (10/12/2010)
WayneS (10/11/2010)
Jeff Moden (10/10/2010)
WayneS (10/10/2010)
Any suggestions on...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2010 at 5:19 pm
mail4sha (10/11/2010)
yes ofcourse..... Perfect guidance... thanks jeff
You bet. Thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2010 at 7:14 am
The Dixie Flatline (10/11/2010)
Jeff, you should check out this thread. It's about a year...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2010 at 7:10 am
GilaMonster (10/12/2010)
Paul White NZ (10/12/2010)
GilaMonster (10/11/2010)
This site was somewhere between terrifying and hilarious - http://www.allinterview.com/showanswers/65496.html
Terrifying. Maybe I will experience some of the humour later, but for now, I'm just...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2010 at 6:46 am
WayneS (10/11/2010)
Jeff Moden (10/10/2010)
WayneS (10/10/2010)
Any suggestions on good, inexpensive, close...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2010 at 6:44 am
... and, no, there is no setting that I know of that will make it otherwise.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2010 at 10:09 am
Please see the following to do what you need...
http://www.sqlservercentral.com/articles/T-SQL/63003/
The embedded comma that you have will cause a bit of frustration on your part but I'm sure you'll be able to...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2010 at 5:37 am
Actually, check out today's article...
http://www.sqlservercentral.com/articles/CTE/71169/
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2010 at 5:24 am
kanika.bhagat (10/11/2010)
create table "student"
(
"rollno" varchar2(4000),
"class" varchar2(4000),
"sem" varchar2(4000),
"sub" varchar2(4000),
"mtt1" number,
"mtt2" number,
"external" number,
"tot" number,
)
output will be like
if we insert values in all the fields...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2010 at 4:41 am
mail4sha (10/11/2010)
http://www.sqlservercentral.com/articles/T-SQL/62867/... i got ur article jeff 🙂
So you're all set then?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2010 at 4:30 am
A word of caution. These solutions are all "Triangular Joins". What are those? Well, a full up CROSS JOIN is also known as a "SQUARE JOIN" so...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2010 at 11:34 pm
The Dixie Flatline (10/5/2010)
It is the CROSSTAB of UNPIVOTS
Is this what we're looking for?
declare @sample table (ID int identity(1,1), Column1 varchar(10), column2 varchar(10), column3 varchar(10))
insert into @sample...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2010 at 11:01 pm
The Dixie Flatline (10/5/2010)
It is the CROSSTAB of UNPIVOTS
Is this what we're looking for?
declare @sample table (ID int identity(1,1), Column1 varchar(10), column2 varchar(10), column3 varchar(10))
insert into @sample...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2010 at 10:53 pm
Viewing 15 posts - 36,361 through 36,375 (of 59,067 total)