Viewing 15 posts - 3,076 through 3,090 (of 6,486 total)
jacob sebastian (5/30/2008)
You can...
May 31, 2008 at 10:15 am
You've given us just about nothing to work with. You going to have to be more specific.
looks suspiciously like something you should be leaving to your presentation layer to...
May 31, 2008 at 9:41 am
With the amount of info you have right here - it's just about impossible to give you anything mucvh to work with. You need to review the execution plan...
May 31, 2008 at 9:38 am
Sounds to me like you're angling towards using some kind of table-wise UNION setup to get your reports. That's certainly something that can be done vai T-SQL.
Depending on what...
May 31, 2008 at 9:26 am
Also - perhaps try setting NOCOUNT on in your stored proc. Messages being returned might be getting misinterpreted too.
May 31, 2008 at 9:18 am
Ted Pin (5/30/2008)
Loner (5/29/2008)
Companies keep saying they can't find the right person, do they know what they are looking for in the first place?
That is a really good point. The...
May 31, 2008 at 9:14 am
In 2005, there are two things that come to mind (well - two different method to get to the same place):
- there's a default trace running, which keeps track...
May 31, 2008 at 9:02 am
Jeff Moden (5/30/2008)
I don't believe anything is missing... just alter the column like I did... don't mess with the constraint or the default.
I understand - I guess I've been focusing...
May 30, 2008 at 10:31 pm
Michael (5/30/2008)
-...
May 30, 2008 at 9:01 pm
Jeff Moden (5/30/2008)
Dunno if it'll work because no one provided the code for the rest of the...
May 30, 2008 at 8:50 pm
Create a passthrough query in Access... Connect it to your DB.
Just type in as the query:
Exec MyStoredProcedureName @Myparameter='MyString'
Save query - run it.....
May 30, 2008 at 8:35 pm
How about making sure the name is unique?
Just create the table, then look up its object_ID(). Doing that will return the #Temp table you created, even if...
May 30, 2008 at 3:25 pm
There should be, although how much might be debatable. Ultimately - I think the "sweet spot" is the version you didn't include:
CREATE NONCLUSTERED INDEX IX_OrderDetailDateProdSold ON dbo.OrderDetail
( OrderDate ASC,...
May 30, 2008 at 12:53 pm
You could always add the constraint with NOCHECK and then enable the constraint. That will prevent any FUTURE nulls from getting in.
May 30, 2008 at 12:29 pm
Have you check if there were nulls in column B? I know you had a constraint on it, but if it was disabled or if the constraint was added...
May 30, 2008 at 12:27 pm
Viewing 15 posts - 3,076 through 3,090 (of 6,486 total)