Viewing 15 posts - 2,431 through 2,445 (of 6,036 total)
Matt Whitfield (9/30/2009)
Like I said, it's not an ideal solution. (<- That's three times now). But, clearly it's an OK solution for the OP, seeing as it seems that is...
_____________
Code for TallyGenerator
September 30, 2009 at 4:25 pm
Matt Whitfield (9/30/2009)
Sergiy (9/29/2009)
That's why SQL Server as well as any other service has no means to tell what procedures will return before the output is actually returned.
Apart from SET...
_____________
Code for TallyGenerator
September 30, 2009 at 8:48 am
Matt Whitfield (9/29/2009)
I'm sure all of that is possible.
I'm pretty sure it's not.
SqlDataReader members give you metadata about data stream ALREADY RETURNED by the query/procedure.
They cannot give you any info...
_____________
Code for TallyGenerator
September 29, 2009 at 11:31 pm
CREATE CLUSTERED INDEX TransactionDetail_AccountDate ON dbo.TransactionDetail(AccountID, [Date])
GO
DECLARE @AccountID INT, @AccountRunningTotal MONEY
UPDATE T
SET @AccountRunningTotal = AccountRunningTotal
= Amount + CASE
...
_____________
Code for TallyGenerator
September 29, 2009 at 9:39 pm
Can you explain the logic of the output?
_____________
Code for TallyGenerator
September 25, 2009 at 7:05 am
"status" indicates a result of actions taken on an entity, or lack of any action.
Every time you query for results of different actions - you name it different statuses.
So, ditch...
_____________
Code for TallyGenerator
September 21, 2009 at 4:18 pm
select * INTO Temp_ CONTACTCALLDETv1
from CONTACTCALLDETv1
where 1=0
Then check the new table columns, find the one of tinyint type and find which one of the sources of the data for this...
_____________
Code for TallyGenerator
September 15, 2009 at 4:17 pm
Put your code into system procedure on master database and execute it like this:
IF EXISTS(SELECT * FROM sysdatabases where name = 'PersonProfile')
EXEC PersonProfile.dbo.sp_MyGrantPermissionProc
If it does not work like...
_____________
Code for TallyGenerator
September 15, 2009 at 10:14 am
Yes, how you build any query depends on desired outcome.
But that obviously was not true:
Either way it will filter the c.contest_id = 2 records.
_____________
Code for TallyGenerator
September 9, 2009 at 9:04 pm
Lynn Pettis (9/9/2009)
Sergiy (9/9/2009)
No, you should leave criteria on "FROM" table in WHERE:WHERE c.contest_id = 2
Only criteria on LEFT JOIN table go into ON.
I think it is a wash...
_____________
Code for TallyGenerator
September 9, 2009 at 7:53 pm
No, you should leave criteria on "FROM" table in WHERE:
WHERE c.contest_id = 2
Only criteria on LEFT JOIN table go into ON.
_____________
Code for TallyGenerator
September 9, 2009 at 4:36 pm
SELECT c.contest_attempts_allowed,
count(ca.ca_status_cd)
FROM contest c LEFT OUTER JOIN contest_activity ca
ON c.contest_id = ca.contest_id AND ca.p_id = 1
WHERE c.contest_id = 2
GROUP BY contest_attempts_allowed
_____________
Code for TallyGenerator
September 9, 2009 at 2:56 pm
http://labs.google.com/papers/bigtable.html
_____________
Code for TallyGenerator
September 8, 2009 at 12:17 am
Marcin Gol [SQL Server MVP] (9/7/2009)
Sergiy (9/7/2009)
Marcin Gol [SQL Server MVP] (9/7/2009)
_____________
Code for TallyGenerator
September 7, 2009 at 4:19 pm
Marcin Gol [SQL Server MVP] (9/7/2009)
_____________
Code for TallyGenerator
September 7, 2009 at 3:19 pm
Viewing 15 posts - 2,431 through 2,445 (of 6,036 total)