Viewing 15 posts - 35,791 through 35,805 (of 59,099 total)
GilaMonster (12/5/2010)
sandippani (12/5/2010)
Have a look to this link :http://www.sql-server-performance.com/articles/per/temp_tables_vs_variables_p1.aspx
However note that the first 'fact' stated in that article is incorrect. Changes to table variables are logged. They don't participate in...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2010 at 3:36 pm
Heh... I found a way around all of the "problems" with WordPress... I write articles on SQL Server instead of blogging. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2010 at 3:22 pm
Brian McGee-355525 (12/4/2010)
If I have a table, columns MYKEY, DT, A, B, C, D, E with the following data:
MYKEY DT ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2010 at 6:27 pm
Heh... <soap box mode on>
I'll agree that some bloatware has caused problems and that data is growing but I think the real problem is that some really sloppy code has...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2010 at 6:10 pm
PaulB-TheOneAndOnly (12/4/2010)
Jeff Moden (12/4/2010)
PaulB-TheOneAndOnly (12/4/2010)
I've seen many tables...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2010 at 4:59 pm
Ah... never mind. The thing I was looking for is in the link you previously posted and it doesn't do quite what I thought. What I thought was...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2010 at 11:58 am
Paul White NZ (11/23/2010)
David.Poole (11/23/2010)
I thought SWITCH only worked in Enterprise Edition?
One can only create partitioned tables on Enterprise, it's true, but ALTER TABLE...SWITCH works regardless of any partitioning.
All tables...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2010 at 11:46 am
Sachin Nandanwar (12/3/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2010 at 11:25 am
michaelwelcome (12/1/2010)
select
d1.auID,
d1.Emp_ID,
d1.dt_Start,
(
select top 1
d2.dt_End
from auData d2
where d2.auID > d1.auID
and d2.Emp_ID = d2.Emp_ID
order by d2.auID
) as dt_end
Emp_Cat
)
from auData d1
where d1.dt_Start is not null
This will...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2010 at 10:37 am
Heh... thanks for the understanding. I just hate making this type of mistake because I'm usually the first one to ask "Really??? You got proof of that???"
I've bookmarked this...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2010 at 10:33 am
PaulB-TheOneAndOnly (12/4/2010)
I've seen many tables where an extra...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2010 at 10:29 am
SQLSmasher (11/30/2010)
The method i can straight away suggest is to use SSIS.
1. Create in-memory single column table with each csv row as table row
2. find COMMA's between "xxxx,yyyy"
3. replace...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2010 at 10:04 am
bhuvan.ram (12/1/2010)
Jeff Moden (12/14/2007)
SELECT * FROM INFORMATION_SCHEMA.PARAMETERS WHERE Specific_Name = 'Award_Category_Insert'Excellent...thanks alot
Thanks for the feedback. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2010 at 9:58 am
I agree with many of the others. This is a "hidden" performance problem that a lot of people don't even consider because they don't know about things like data-type...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2010 at 9:54 am
Where in DelimitedSplit8K do you find a physical Tally Table?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2010 at 11:14 pm
Viewing 15 posts - 35,791 through 35,805 (of 59,099 total)