Viewing 15 posts - 35,041 through 35,055 (of 59,099 total)
Grant Fritchey (2/15/2011)
Jeff Moden (2/15/2011)
Grant Fritchey (2/15/2011)
Define a clustered index on the column that appears most frequently in the WHERE clause of SELECT
statements.
But not in JOIN criteria? No,...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 12:16 pm
ganeshkumar005 (2/15/2011)
UPDATE tlstagingdb.dbo.tbltlxyz SET lImpStatus = 10 where limpidentity in ( select xxxxxxxxxxxxxxxxxxxxx)
select subquery works excellent and the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 8:14 am
karthimca07 (2/15/2011)
checksum uses more resources in my case.as i have to check more than 20 columns off different types.
how columns_updated works?
if want random columns means how do i please help
Columns_Updated...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 8:08 am
Grant Fritchey (2/15/2011)
Define a clustered index on the column that appears most frequently in the WHERE clause of SELECT
statements.
But not in JOIN criteria? No, no way. The basic...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 7:46 am
Gail and Grant (or anyone else that can jump in),
The article also has the following statements:
...[font="Arial Black"]whereas, with a nonclustered index the leaf level contains the address to the data...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 7:30 am
chintalagiriprakash (2/14/2011)
i donot know why it is not working i wrote the query as u mention in the link but i could not get the result
thanks...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 12:11 am
nadabadan (2/14/2011)
At the bottom of this white paper are links to three other decent xml...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2011 at 11:12 pm
sql_butterfly (2/14/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2011 at 11:08 pm
darryljm (2/14/2011)
Example I have two tables "Labor" and "Parts" need to return as followsLabor field 1
Part1
Part2
Part3
Labor field2
Part1
Part2
Part3
Any help would be appreciated
I believe you should only have 1 labor field in...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2011 at 10:02 pm
frecapi (2/14/2011)
No I didn't think about that. Something like:Select ID, apn, (select permit_1 from #mytable), from #mytable union all
Select ID, apn, (select permit_2 from #mytable), from #mytable....
Yep... kind of....
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2011 at 10:00 pm
You might also want to do a server side trace and find out what's using most of the CPU time.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2011 at 9:54 pm
frecapi (2/14/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2011 at 9:01 pm
nico van niekerk (2/14/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2011 at 7:03 pm
Oh yeah... I forgot to mention it... it handles a space as a delimiter, as well.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2011 at 6:56 pm
Here's my latest splitter. I'm still testing it to be included in the rewrite of the "Tally Table" article but it blows the doors off the old splitter especially...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2011 at 6:55 pm
Viewing 15 posts - 35,041 through 35,055 (of 59,099 total)