Viewing 15 posts - 53,011 through 53,025 (of 59,091 total)
Ys just gotta love Bulk Insert for speed... 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2008 at 11:53 pm
If you don't want to use BCP with a format file (absolutely the fastest), then something like this is probably in order... brute force 😉
USE AdventureWorks
GO
SELECT STR(SalesPersonID,3)
...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2008 at 11:50 pm
If you ever need to avoid the use of xp_CmdShell (lot's of DBA's simply don't allow its use for security reasons), then check this out...
EXEC Master.dbo.xp_DirTree '\\MIS1\Tmandaily$\INCT\',1,1
Won't help you with...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2008 at 5:37 pm
I use the Bulk Insert command from T-SQL... I don't even go near SSIS for the same reason I don't use DTS in 2k... too slow. I can import...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2008 at 5:13 pm
but i have the following error :
37000(7405)[Microsoft][SQL Native Client][SQL Server]Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set for the connection. This ensures consistent query semantics. Enable these...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2008 at 5:08 pm
I believe "spooky" was about
SELECT * FROM SYSOBJECTS
WHERE name = '#MyTempTable'
Yeah... I missed that... not exactly the right way to check for temp tables.
Thanks for the information on the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2008 at 5:00 pm
timothyawiseman (1/9/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2008 at 4:56 pm
Also, in the article there was a code block that didn't show up properly. It was after
The next thing folks might try, is a full "covering" index...
Could you provide what...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2008 at 4:49 pm
Good idea... in fact, that's exactly what my code does... but there's nothing in the data to determine what level a node is at... just the parent ID, etc... and...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2008 at 1:53 pm
Perfect... thanks for the feedback, Shaun.
To keep conflicts with the Left and Right keywords to a minimum, I use LeftBower and RightBower in my code. A "bower" is one...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2008 at 1:48 pm
He has code that inserts and increases the left and right indicies... most of my code is batch code so I just recalc the whole tree from the adjacency model.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2008 at 8:59 am
Shaun McGuile (1/9/2008)
Ok I found ithttp://www.dbmsmag.com/9603d06.html
Whoa thats like 12 years old almost. 😀
--Shaun
Heh... yeah... the good stuff never changes 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2008 at 8:04 am
Shaun McGuile (1/9/2008)
Jeff do you have a link to Celko's "nested model"?--Shaun
You bet...
http://www.ibase.ru/devinfo/DBMSTrees/sqltrees.html
If memory serves, the code that creates the nested model has a minor error in it... it leaves...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2008 at 7:48 am
berto (1/9/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2008 at 7:32 am
The question is wrong on the basis of design and the modeling of the parent child relationship using one column is totally flawed.
Actually, I believe the whole "adjacency model" thingy...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2008 at 7:25 am
Viewing 15 posts - 53,011 through 53,025 (of 59,091 total)