Viewing 15 posts - 55,336 through 55,350 (of 59,098 total)
I hate it when fish smells like rotten eggs ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 21, 2007 at 8:32 am
No problem, Michael. But I am curious what the OP actually wants... it looks like he's trying to display the tree for a current drill down into a set of...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 21, 2007 at 8:30 am
Um... what do you mean by "manually eiditing the table"?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 20, 2007 at 11:12 pm
Dollars to donuts the views are aggragate views that either return to many columns or might even have views of views or UDF's.
Also, any of these tables have a primary...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 20, 2007 at 11:05 pm
Don't change anything that's owned by the system... period.
Make a copy of sp_SpaceUsed under a different name and then make all the changes you want.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 20, 2007 at 10:55 pm
Heh... 5 rows for 2 users generates 1,460 rows in the #Days table to start with. Wonder what's going to happen when you have 10,000 rows for 100 users? --Jeff Moden Change is inevitable... Change for the better is not.
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
August 20, 2007 at 10:53 pm
I'm thinking that DTS is going to be your only way out if you don't want to or can't use a command prompt of xp_CmdShell.
If you had a really cool...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 20, 2007 at 5:50 pm
Peter, any way you guys can suppress the double spacing? And, which editor are you using (I like the colors) ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 20, 2007 at 5:45 pm
Uh-huh... What is that that you would like to do for the following?
ID Name ParentID Level
1 Root null 1
2 Trunk 1 2
3 Branch 2 3
4 Leaf 3 4
5 ...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 20, 2007 at 5:43 pm
Why are you storing such data in your database? Can't you get the source info into a little better shape, first? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 20, 2007 at 5:24 pm
The best performance will come from BULK INSERT followed closely by BCP in most cases. But "What is Best" is in the eyes of the beholder... If you need the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 20, 2007 at 4:40 pm
No... not more VB like... more mathematical like ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 20, 2007 at 4:15 pm
Sure would be nice if you posted the URL of the article you read... ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 20, 2007 at 4:06 pm
Sounds like an interesting article... do you have the link? I'd like to take a peek...
Thanks, Tracey.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 19, 2007 at 9:35 am
Heh... ok... no flaming
But I'll just bet you'll never again let another vendor touch your DB's without making a full backup, huh?...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 19, 2007 at 12:30 am
Viewing 15 posts - 55,336 through 55,350 (of 59,098 total)