Viewing 15 posts - 47,596 through 47,610 (of 59,099 total)
Parul Sharma (10/24/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2008 at 5:01 pm
AnzioBake (10/24/2008)
either one of the following does what you are asking. The Second query is marginally faster...
Both methods use a "triangular join" which, because of the way it's used,...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2008 at 4:59 pm
I think it would be best that if the function receives a NULL, it should return a NULL. NULL has the special meaning of "unknown" and changing it to...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2008 at 4:38 pm
Try this...
SELECT COUNT(*)
FROM dbo.RentalHistory
WHERE FromDate >= DATEADD(mm,DATEDIFF(mm,0,'20080901'),0)
AND ToDate < DATEADD(mm,DATEDIFF(mm,0,'20080901')+1,0)
... and there's only 4 items in...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2008 at 4:18 pm
Greg Snidow (10/25/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2008 at 4:01 pm
GilaMonster (10/25/2008)
Jeff Moden (10/21/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2008 at 3:59 pm
1mwalsh1 (10/25/2008)
Working with SQL Server 2008 Express, I am trying to match user answers to correct answers and tally up the score. Tables are as follows;
Answers
GameNo
Ans1
Ans2
Ans2... etc.
PlayerAnswers
GameNo
Player
Ans1
Ans2
Ans3... ...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2008 at 11:18 am
Jerry Hung (10/25/2008)
See forum best practicehttp://extras.sqlservercentral.com/prettifier/prettifier.aspx
Heck... make it as pretty as you want... that's only part of the "best practice". What is a "best practice", though, is actually posting...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2008 at 11:16 am
baumgaertner (3/31/2008)
But I do not want to rename the table and then insert the data to the new table.
When you have big tables this approach...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2008 at 11:05 am
It sounds like you're passing each stage as a parameter and that you're looping through each stage. It sounds like each stage may be different enough where you are...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2008 at 9:54 am
First, what do you get when you run the following?
SELECT * FROM tabUserInfo
Where (UserID Is Null or UserID <= 0)
Now, what do...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2008 at 9:48 am
If the table is that large, consider splitting it into smaller tables based on a PK and then build a partitioned view to put it all back together again. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2008 at 9:38 am
smunson (10/24/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2008 at 9:31 am
I guess I'd have to argue that developers are sometimes even more arrogant than the DBA. What makes a GUI developer think (s)he knows something about how to store,...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2008 at 9:17 am
Doing it the old fashioned way using a "Derived table" instead of a CTE...
SELECT orig.AgentID, orig.AgentType
FROM #a orig
INNER JOIN
...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2008 at 8:43 am
Viewing 15 posts - 47,596 through 47,610 (of 59,099 total)