Viewing 15 posts - 16 through 30 (of 362 total)
aturner51, To be truthfull, I do not access my SPs using VBs ExecuteNonQuery(), therefor I do not know the proper VB syntax...
May 25, 2004 at 11:07 am
David, I do not know your data, and can not know what the "best" method will be for you, but have you considered putting the data from the tbl_Site_parameters table...
May 25, 2004 at 9:52 am
As far as the "derived" table usage, give this a try...
Replace your entire WHERE clause with something like...
INNER JOIN (
SELECT TOP 1
[Data_Cube_Minimum_Shipment_Date] as MinDate,
[Data_Cube_Maximum_Shipment_Date] as...
May 25, 2004 at 9:48 am
In some instances adding an index or a clustered index to the #Temp table can greatly enhance perfomance. This is one thing that that #Temp tables have over the other methods,...
May 25, 2004 at 9:36 am
Sure, just create the VIEW with an expression for you date column data. However, you will not be able to UPDATE the "date" data using this VIEW. (Maybe see TRIGGERs - INSTEAD...
May 25, 2004 at 9:30 am
Can you supply an example script with a call to your SP in context?
This may help me understand exactly what you are looking for.
May 25, 2004 at 9:23 am
You are accessing the data from tbl_Site_parameters table within a "derived" table structure. Within this structure you can not access values from outside the structure.
Try JOINing the tbl_Site_parameters table without...
May 25, 2004 at 9:20 am
NP, glad it worked for you. I know it seems easier to code the multiple SELECT ... INTOs, but the single SELECT ... INTO ... WHERE 1=2 to create the...
May 25, 2004 at 9:12 am
Neil,
What column specifically did you change?
Did you ALTER the view after to made the column name change?
Has the WHERE clause shipment date span changed? Run the SELECT TOP 1 *...
May 25, 2004 at 8:16 am
Seems you can not create the same #Table twice in a script, even if you DROP it in between.
How about something like this (if structure is the same for either)
IF...
May 25, 2004 at 8:06 am
I found a solution that works for what I need.
Since the "Product" data in the #TempGroups table is numeric,
I could use this to my advantage:
Instead of (1st Step)
Insert...
March 25, 2004 at 7:08 am
My understanding, and what I've noticed...
If an underlying "real" table is accessed WITH NOLOCK, the only "locks" on that table would be a "Schema" lock that could prevent structural changes...
March 23, 2004 at 11:32 am
One thing about SPs, as opposed to client / mid tier, is the code is more exposed. This has never been an issue for me, but it may be to...
March 22, 2004 at 11:43 am
Greg, It might be the "SP Hater" likes Views for limiting access to and from the data, and yes, I think most of us agree that Views are great "tools"...
March 22, 2004 at 9:35 am
Nice, to the point... always a good "reminder". Seems coding for NULLs is like making backups, as soon as you don't, you get bit
March 15, 2004 at 9:00 am
Viewing 15 posts - 16 through 30 (of 362 total)