Viewing 15 posts - 53,386 through 53,400 (of 59,072 total)
The best thing to do would be for your organization to hucker down and fix the poorly written code by turning them into viable stored procedures or views.
Than notwithstanding, what's...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 11:31 am
You must use Dynamic SQL to do such a thing...
CREATE PROCEDURE [dbo].[sp_vcGetStop]
@CheckTable varchar(15),
@Sequence numeric(10,0)
AS
EXEC ('SELECT CUID As Rt, WorkType FROM ' + @CheckTable + ' WHERE Sequence = '...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 11:26 am
There is a registry setting that prevents SQL Server from being able to use OpenRowSet... look in the registry for "DisallowAdhocAccess" and change it's value to zero.
Also, OpenRowSet creates temporary...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 11:14 am
I agree with Steve, but the code is so simple I wouldn't make a stored procedure or function for it... too much overhead for such a simple thing.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 11:04 am
Which type of DBA? If it's the "System" DBA, you'd better trust him/her... they need total access to really do the job correctly. If it's an "Application" DBA,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 11:02 am
I agree with Steve in avoiding ## Global Temp Tables... if two procs (or the same proc running more than once) attempt to create a GTT (Global Temp Table) of...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 10:59 am
Although you can have only 1 Primary Key (hence the word "Primary"), you can, in fact, have multiple UNIQUE keys in the form of UNIQUE indexes. Keep in mind...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 10:57 am
Without seeing the offending code, the short answer would be simply to rewrite the code so that it's performance enabled. Step 1... avoid cursors. Step 2... avoid 99.9%...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 10:51 am
Great code and explanations, but no test data...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 10:47 am
First, dunno how to post CF code on this forum mostly because I've never used CF.
Still need to see code... I see that you've created a function to use the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 10:28 am
Outstanding! Thank you so much for the feedback, Troy. Very happy to have been able to help.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 10:23 am
vinno369 (12/26/2007)
Jeff, unfortunately dropping the stored procedure in to Master is not an option for me.
Then, unfortunately, you're gonna need some form of loop and some dynamic SQL with a...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 10:21 am
jacob sebastian (12/25/2007)
Jeff Moden (12/25/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 10:11 am
Post the code that you tried, Tony... it's the only way we can see what might be wrong...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 9:55 am
I know a lot of people hate the idea but this is where I'd say "enough is enough" and drop the proc into the Master database and be done with...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 25, 2007 at 9:20 pm
Viewing 15 posts - 53,386 through 53,400 (of 59,072 total)