Viewing 15 posts - 53,041 through 53,055 (of 59,072 total)
Have you taken the time to verify that you actually have the problem?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2008 at 7:39 am
Dunno about that... but I do know that throwing indexes at tables will absolutely not help code that is written incorrectly because the code will not be able to use...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2008 at 7:37 am
Perfect... thanks for the feedback.
Yeah, anytime you have a join on different datatypes, it must do an implicit conversion to do the join... best you can get out...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2008 at 7:35 am
You see the need to split a parameter with more than a million characters?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2008 at 7:31 am
It will only show some pointer information in the Grid mode... you must be in the Text mode to see the data from a Text datatype.
Best thing to do would...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2008 at 7:26 am
If you feel that you must split application code to make it easy to find, create a new database for each application... store only code and definition tables in these...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2008 at 7:23 am
Heh, heh... in my shop, yes... 😛
Check the following URL... someone made the terrible mistake of naming tables and objects after customers and now he's in a bit of trouble...
http://www.sqlservercentral.com/Forums/Topic439936-5-1.aspx
Do...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2008 at 7:17 am
This will do it... could turn it into a function...
DECLARE @PurchaseReqNo VARCHAR(50)
SET @PurchaseReqNo = '12,241,342,34234'
DECLARE @TempTab TABLE (Element INT IDENTITY(1,1) PRIMARY KEY CLUSTERED, ReqQty INT)
INSERT...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2008 at 7:06 am
If you have TempDB set up to auto-grow by 10% like everyone else seems to, it will cause 73 fragments as it grows to 1 gig. And, I agree...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2008 at 6:45 am
Just so you know... Books Online comes with SQL...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2008 at 6:35 am
The beating is better...
If the code must ever be executed more than once, it will fail because the tables in the two or more instances of the proc will be...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2008 at 6:29 am
Sandy (1/7/2008)
Hey Jeff,I just asked my question not what you suggested me.
I clearly understood what you suggest me, only generic name for the Database Objects.
Didn't look that way to me,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2008 at 10:22 pm
antonio.collins (1/7/2008)
i don't think a numbers table is ever necessary.
What do you use SQL Server 2000, instead?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2008 at 10:17 pm
Yeaup, we all need rules... but to keep from becoming a non-thinking "SQL Clone", ya gotta read about the "5 Monkeys Experiment"... you'll see what I mean... 😉
http://www.lanebaldwin.com/v03I8.htm
Dunno if there's...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2008 at 10:07 pm
If you use the extra parameter I posted in 2k or 2k5, it will also...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2008 at 5:32 pm
Viewing 15 posts - 53,041 through 53,055 (of 59,072 total)