Viewing 15 posts - 53,461 through 53,475 (of 59,072 total)
Yes, it is possible... read the following article... because these are a bit "tricky", make sure that you read and understand the entire article before you try anything like that...
http://www.sqlservercentral.com/articles/Administering/utilityprocedures/2272/
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 8:35 am
Midan,
What John is asking for is covered in the following URL...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
You have a lot of data posted... we should use your data to give you the best answer. As...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 8:12 am
Hear! Hear! We've invoked similar rules.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 7:53 am
You bet...
... and, there are two "f's" in "Jeff"... I know a name isn't much, but it's all I've got 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 7:18 am
karthikeyan (12/21/2007)
Thanks.Suppose if i have like this,
Declare @Str varchar(300)
@Str = 'Karthikeyan,Madhivanan,JeffModen,Steve-Jhones,MattMiller,GilaMonster'
do we have to repeat your code for 6 times? Suppose if i have around 20 names do we repeat...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2007 at 7:15 am
I don't believe so... other than running it or taking it apart and running the peices...
You could always setup to exec it and run an estimated execution plan on it,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2007 at 1:16 pm
Heh... I hate Oracle...
I create a linked server to the Oracle DB, grab the data I need and store it in permanent "working" tables in SQL Server, and then all...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2007 at 1:05 pm
GilaMonster (12/20/2007)
Run sp_updateusage
THAT would be the ticket...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2007 at 1:02 pm
p.s. Don't forget to close the spreadsheet after you save it or you WILL get an access error... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2007 at 1:00 pm
No, no... it's much easier than any of that. This is a common problem and DTS frequently messes up imports especially if there are some merged cells above the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2007 at 12:45 pm
Ok... here's the code that proves what the problem is... it's not my code, but I forget the name of the good fellow that wrote it for me as a...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2007 at 11:24 am
Basically it is a proprietary SP provided by a SQL based web application for the purpose of generating unique integer based row IDs. It does several things including calling other...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2007 at 11:03 am
Thanks for the feedback, but to be sure... cursors are never an option for me. Maybe the occasional WHILE loop to act as a control for managing "dips" to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2007 at 10:20 am
Bottom line, sometimes it's just like magic to make the code work Not to mention the ohs and ahs from the staff who were just going to open the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2007 at 10:13 am
It was in 2k... Heh... I'm thinking that there's a hidden "bookmark" that didn't show up in the EP. But, correct, it does show that just because an index...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2007 at 10:01 am
Viewing 15 posts - 53,461 through 53,475 (of 59,072 total)