Viewing 15 posts - 40,276 through 40,290 (of 59,072 total)
Since you're brand spanking new to the forum, I recommend you read the following... people will be a lot more willing to help if you help them help you.
http://www.sqlservercentral.com/articles/Best+Practices/61537/
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2010 at 8:51 pm
shaini.binu (1/14/2010)
Thanks for the quick reply,
Regarding the requirement ,
In LinkTable , ID1 contains the uniqueid of a transaction and ID2 contans the uniqueid of the transaction related to it,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2010 at 8:45 pm
I'm not a GUI programmer and it's been years since I've touched even VB6 never mind VB.Net. But it sounds like a cursor (GAH!) could serve as a "subroutine".
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2010 at 8:32 pm
SELECT t1.ID, t1.Name, t1.ID AS Numbering,
(SELECT COUNT(*) AS NumberOfFruits FROM Test t2 WHERE t2.ID = t1.ID) AS NumberOfFruits
...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2010 at 9:03 pm
Grant Fritchey (1/13/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2010 at 7:49 pm
Outstanding. Thanks for the feedback. C'mon back if you get stuck.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2010 at 7:37 pm
Rome1981 (1/13/2010)
I was just about to post the same. Good to know there are people testing these solutions/examples.Jeff- That is very good advice, I did not know that.
Thanks for the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2010 at 9:13 am
peter-757102 (1/13/2010)
Because of this, it makes sense to do a reverse of only the last...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2010 at 9:10 am
Jeff Moden (1/13/2010)
Don't get me started on what a poor metric the number of 'logical reads is'
Heh... now you know why I couched it all in "It Depends". ...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2010 at 9:09 am
Paul White (1/12/2010)
Jeff Moden (1/12/2010)
Check again... op asked for mm/dd/yyyy hh:mm. Above code returns yyyy-mm-dd hh:mi 😉
Assuming you don't mind using the Microsoft version of the Kuwaiti algorithm of...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2010 at 5:22 am
Good article and makes a lot of sense... providing that the table doesn't have a lot of inserts where every index counts AGAINST inserts. Most people don't know that...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2010 at 12:26 am
imhemal29 (1/12/2010)
Select Cast(convert(varchar(16),Getdate(),120) as DateTime) as [Date]And
Select convert(varchar(16),Getdate(),120) as [Date]
Check again... op asked for mm/dd/yyyy hh:mm. Above code returns yyyy-mm-dd hh:mi 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
January 12, 2010 at 11:27 pm
lobbymuncher (1/10/2010)
bitbucket-25253 (1/9/2010)
http://www.sqlservercentral.com/Forums/Topic844889-392-1.aspx
It is one of the worst I have seen on SSC in a long long time.
Lynn - I must compliment you on your...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 12, 2010 at 11:21 pm
Yes... it's absolutely possible. I realize that you've tried a couple of posts on dynamic SQL and haven't been able to get it because you're "new". However, you...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 12, 2010 at 10:26 pm
rnikandrov (1/8/2010)
here is a sample:
A 919934 [tab] 1 [tab] jason
B 2222 [tab] 999999 [tab] 111111 [tab] 1113
C 2...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2010 at 8:56 pm
Viewing 15 posts - 40,276 through 40,290 (of 59,072 total)