Viewing 15 posts - 46,531 through 46,545 (of 59,101 total)
Ninja's_RGR'us (12/18/2008)
There's a question, it's just not obvious.The guy abviously has troubles with the english written language. Nothing to be made fun of guys!!!!!!1
Actually, there is... it's people like...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2008 at 7:16 am
sausage.dog (12/17/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2008 at 11:54 pm
gcopeland (12/17/2008)
Jeff Moden (12/17/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2008 at 11:48 pm
RBarryYoung (12/17/2008)
Jeff Moden (12/17/2008)
Also, have you given any thought to using a hybrid of the Nested Set Model instead of the Adjacency Model you're currently using?
Actually, Jeff, I believe that...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2008 at 11:42 pm
psmg01 (12/17/2008)
Thank you for your reply.
I will post this in T_SQL forum too.
I am having a table like below
[CREATE TABLE [dbo].[Output_Info](
[Common_Id] [int] NOT NULL,
[Signal] [real] NOT NULL,
[Detect] [nchar](10)...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2008 at 11:38 pm
Way cool... finally, a good use for such a thing. Might I suggest you "baseline" the table by saving the output of the query I gave you in a...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2008 at 11:30 pm
Sergiy (12/17/2008)
dejanette.gordon (12/17/2008)
How do you sort alphanumeric data in sequential order? I need the data to go from:
100
101
102
etc...
The answer is:
ORDER BY AlphanumericValue
Now, THAT's entertainment! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2008 at 11:27 pm
dejanette.gordon (12/17/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2008 at 11:27 pm
Gabe (12/15/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2008 at 10:12 pm
Oh yeah... almost forgot... the method I described that uses multiple tables, a constraint, and a view to make a "partitioned" view, is being deprecated. If you have no...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2008 at 8:20 pm
As already stated, this is a very bad idea because of several reasons and I might be missing a couple...
1. First of all, by definition, a "column" in a...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2008 at 8:13 pm
As Seth's good question implies, the idea of reusing numbers or recovering missing numbers in an IDENTITY sequence is something you should consider not worrying about at all. Contiguous...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2008 at 7:36 pm
michael vessey (12/17/2008)
I use a function to turn comma separated lists in varchars into tables (don't ask - i know it breaks 1st nornal form - it's something i inherited)
Nicely...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2008 at 7:20 pm
We assign all such ownership as "dbo"... prevents such hassles in the future.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2008 at 4:45 pm
SSIS, CmdShell/BCP, OPENROWSET, or Text based linked servers... each of which are in Books Online.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2008 at 4:43 pm
Viewing 15 posts - 46,531 through 46,545 (of 59,101 total)