Viewing 15 posts - 53,506 through 53,520 (of 59,072 total)
See what I mean, Marcus? No... no one wrote 100% of the code you needed... but, unless I miss my guess, David's code will be very easy for you...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 1:23 pm
Sorry... I didn't say it quite correctly... if the table is preformed with an IDENTITY column, you'll be ok... it's actually when you use the SELECT/INTO with the IDENTITY function...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 1:00 pm
The table name cannot be variable without using some form of dynamic SQL... kinda like...
DECLARE @TableName SYSNAME
SET @TableName = 'sometablename'
EXEC ('SELECT * FROM ' + @TableName)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 12:13 pm
Thanks for the feedback, Matt...
I suppose the reason why I only got 40% improvement out of SELECT/INTO is because I'm running an "ancient" 5 year old P5 running at...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 12:02 pm
grkanth81 (12/19/2007)
Hey guyz...can anyone help me with the probs i have mentioned in the post...
thnx...
Well, at least that's a polite way to "bump" your post... 😉 This isn't "instant...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 11:49 am
Oh, sorry... yes, your query is the ticket... mine is wrong.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 11:15 am
Perhaps, something like this...
select first_name
,last_name
,government_id
from people
where government_id like '[0-9][0-9][0-9]-%'
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 11:03 am
... and no... I don't recommend using two loops 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 10:37 am
Marcus Farrugia wrote:
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 10:34 am
Your comments wise guys! 🙂
I know what your meant, but just so you know... the term "wise guy" in many English speaking countries is usually considered to be a fairly...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 9:03 am
...almost forgot... the "words" you're looking for are "Parsing a delimited column".
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 8:11 am
If you really want help, refer to the following article...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 8:09 am
Ummm... what's not in Books Online is the fact that the DATETIME datatype is a "fixed position float". I know... sounds contrary... what I mean is that DATETIME datatypes...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 8:07 am
The addition zero is coming from the fact that it's automatic code... it figures out that the "Page1" entry is 5 characters long and uses that asthe length for all...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 7:44 am
Thanks David... appreciate the explanation...
Yeah, I figured the Stuff and Group By out for the single table application... just didn't understand it for the two table application. Now, I...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 7:40 am
Viewing 15 posts - 53,506 through 53,520 (of 59,072 total)