Viewing 15 posts - 37,846 through 37,860 (of 59,072 total)
davec-640463 (6/30/2010)
It also sounds like table variables could help you out here. You could possibly subset your data into table variables perfoming some of the logic you describe....
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 7:17 am
As a sidebar, I'd use format 112 so the file names are sortable.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 7:11 am
Duncan Pryde (6/30/2010)
Banging my head for a while, I finally found this page, where someone suggests looking at the SET options.
Heh... I plain forgot about that possibility because we have...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 7:06 am
Mike C (6/29/2010)
CREATE TABLE #Role
(
RoleName VARCHAR(100)
);
GO
INSERT INTO #Role
(
RoleName
)
VALUES ('Accounting'), ('Approver'), ('Developer'), ('International Sales Manager'), ('Marketing'), ('System Administrator'),
('Technical Customer'), ('Technical Director'), ('Training');
GO
CREATE TABLE #UserRole
(
UserID INT NOT...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 6:53 am
gideon.kahl (6/29/2010)
WayneS (6/29/2010)Out of curiousity, did you use the first solution as it's written, or did you follow the recommendation to build your very own tally table with a clustered...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 6:42 am
Heh... I finally beat Grant to the punch for a change. ๐
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 6:35 am
aravind-305595 (6/29/2010)
I have an existing code in sql server 2000, which after migrating to sql server 2008 the performance has become poor.
The query inside the code have a select statement...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 6:32 am
I don't use SSIS so I have no clue but let my post serve as a "bump" to someone who may. ๐
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2010 at 9:13 pm
Eugene Elutin (6/29/2010)
Hornestly, I believe that your question is not really for a forum discussion. It is too many factors which would determine the best solution for your company....
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2010 at 9:10 pm
Duncan Pryde (6/29/2010)
Does anyone have any ideas what I should try looking at to get this working?
Yes... Google for "Parameter Sniffing" for the reason caused by multiple causes and repaired...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2010 at 9:01 pm
Michael Valentine Jones (6/29/2010)
Dan.Humphries (6/29/2010)
...I have never gotten the snarky type of responce that is so normally typical on other IT boards...
It's not all love and kisses around here; Check...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2010 at 8:57 pm
lmu92 (6/29/2010)
WayneS (6/28/2010)
lmu92 (6/28/2010)
The first person who "forced" me to do it actually...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2010 at 8:42 pm
lmu92 (6/29/2010)
torpkev (6/29/2010)
I was pretty close in what I had but wasn't quite there.. and the link on dynamic cross tab sounds pretty interesting -...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2010 at 8:28 pm
Dohsan (6/29/2010)
Having a read of this article should help you:
Actually, I have to admit, my really cool (or so I thought :blush: )method got the pants beat off it by...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2010 at 8:22 pm
All good ideas, Wayne. Thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2010 at 7:49 pm
Viewing 15 posts - 37,846 through 37,860 (of 59,072 total)