Viewing 15 posts - 37,861 through 37,875 (of 59,098 total)
Agreed.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2010 at 6:13 am
We drove secondary ads for Expedia.com. A single SQL Server handled things just fine. It was more important to balance 3 identical web servers that had a pretty...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2010 at 6:10 am
niall.baird (6/30/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 9:25 pm
What is the reasoning behind NOT showing 101?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 5:12 pm
I forget who I got this one from but I've never found anything simpler for correctly calculating age in years. Using Lynn's good test harness...
CREATE TABLE #T(Id INT,date1 DATETIME,date2...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 5:05 pm
PaulB-TheOneAndOnly (6/30/2010)
sudhakara (6/30/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 4:15 pm
david_wendelken (6/30/2010)
It's also easier to comment out a line starting with a comma when debugging.
Actually, it's not. It's only easier to comment out the last line with leading commas....
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 3:41 pm
Heh... almost 1000 lines of trigger code with cursors and multiple table updates with some pretty nasty joins and you wonder why there are deadlocks occurring. My suggestion would...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 3:30 pm
davec-640463 (6/30/2010)
Jeff Moden (6/30/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 7:57 am
Minaz Amin (6/29/2010)
Try using GROUPING SETS ,ROLLUP or CUBE with group by function.
Agreed and Spot On.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 7:37 am
leonardo_gt (6/30/2010)
To obtain a single value as a result of an operation...
That's normally the end of any chance at performance. Stop thinking about what you want to do to...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 7:33 am
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
Viewing 15 posts - 37,861 through 37,875 (of 59,098 total)