Viewing 15 posts - 31,276 through 31,290 (of 59,101 total)
preetpalkapoor (2/5/2012)
create table info (id int,name text,class varchar(50))
insert...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 12:14 pm
J Livingston SQL (2/5/2012)
....really should have seen that, rather than just coding my "thought" process on how to break it out into what I required....:-)
Nah. I do things just...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 12:01 pm
Hi Chrissy,
You can always use an iTVF or Inline Table Valued Function for such a thing. They're very fast. This one will look a bit odd to you...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 1:21 am
The main difference between Full & Bulk logged is that [font="Arial Black"]all[/font] the Bulk Load operaions are minimally logged into the log file of the databases
Actually, that might not be...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 12:10 am
What's not to be happy with there? It could be shortened a bit but would still be basicly the same thing.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 12:00 am
sergeyledenev (2/4/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2012 at 11:56 pm
J Livingston SQL (2/4/2012)
prod_id SumQty
------- -----------
p2 11
p3 16
if you provide the create table / insert data scripts as I...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2012 at 11:37 pm
CELKO (2/4/2012)
The best practice is not to write dialect SQL and stick to ANSI/ISO syntax
Heh... you've been saying that for years but I've never seen you post a free link....
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2012 at 11:11 pm
What can I say? I was looking to see if anything else needed to be added and you've covered it all. Nicely done.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2012 at 3:18 pm
CELKO (2/2/2012)
You misssed a lot.
Maybe so but the article had a single purpose which was mostly covered.
ISNULL takes only 2 parameters whereas COALESCE takes variable number of parameters
Something else might...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2012 at 3:14 pm
Jing. (2/3/2012)
go
INSERT INTO student
select 1, 'kiran', 5 UNION ALL
select 1 ,'kiran', 10 UNION ALL
select 1 ,'kiran', 15 UNION ALL
select...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2012 at 7:50 am
ashutosh.kumarpandey (2/3/2012)
Select * from student where stdnt_id not in (select stdnt_id from student where stdnt_activity=15)
this will take sometime however your can easily optimize it but that I will leave...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2012 at 11:02 am
GilaMonster (2/2/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2012 at 6:37 am
prashantgoswami2007 (2/2/2012)
Actually, you might want to explain why you wrote code that takes 10 times longer to run, returns duplicate answers, can't be easily modified to solve for other similiar...--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2012 at 6:29 am
srikant maurya (2/2/2012)
create table student ( stdnt_id int, stdnt_name varchar(50),stdnt_activity SMALLINT )
go
INSERT INTO student
select 1, 'kiran', 5 UNION ALL
select 1 ,'kiran', 10 UNION ALL
select 1...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2012 at 6:22 am
Viewing 15 posts - 31,276 through 31,290 (of 59,101 total)