Viewing 15 posts - 31 through 45 (of 529 total)
For the second case, it is rather simple.
Just do a joining update ...
UPDATE ComponentOrders
SET OrderDescription = CASE WHEN Component.OrderId <= 100 THEN 'First 100 orders' ELSE...
November 7, 2003 at 4:30 am
Depending on your needs, you could use 'updateable views'. Some restrictions apply, so you should check them against your needs.
Another solution (f you don't want to use multiple recordsets) is...
November 3, 2003 at 5:11 am
There is no way in which you can pass a tablename as a parameter (without using dynamic SQL). Unless you write a huge IF THEN ELSE structure for each possible...
October 31, 2003 at 9:51 am
Why the requirement to put everything in one trigger? Makes life complicated, I think...
You can write a trigger on all three actions.
CREATE TRIGGER tr_InsUpdDel ON tableA
FOR...
October 31, 2003 at 9:19 am
From BOL:
quote:
All expressions must be of the same type or must be implicitly convertible to the same type.
October 31, 2003 at 3:33 am
Your original solutions seems OK. The only problem could be if your job that disables the datapopulatejob1 is stuck for some reason, the datapopulatejob1 might never run. And you won't...
October 31, 2003 at 2:46 am
I am pretty sure updating records in batches, in stead of the whole table at once will not improve performance overall.
It does give you other advantages like locks being released,...
October 31, 2003 at 2:41 am
quote:
I tried to add an extra partition (one for each year) but then get the error "User-defined partitions are available only if...
October 30, 2003 at 8:09 am
With 20 CAL's, you can only have 20 concurrent users. For a webserver, one user can be compared to a single session on IIS.
So for every (concurrent) visitor of any...
October 30, 2003 at 6:51 am
Alternative solution using (self)joins :
Select P1.part,
P1.Result - P2.Result As Result,
P1.locationTo,
...
October 28, 2003 at 10:19 am
This is not possible as you write it. Your solution is to use 'dynamic SQL'. Check BOL for 'EXEC'.
Your code would look something like :
CREATE PROCEDURE...
October 28, 2003 at 8:12 am
IMHO, best practice if you want an extensible system, is to have one base table, say with all the persons filling in the questionnaire; one table with all the questions...
October 27, 2003 at 9:05 am
I was not saying that using a bitmasked field is bad...
I do believe it has some uses, on the other hand, there are some drawbacks. Just tried to list some.
I...
October 27, 2003 at 9:01 am
One way could be to add a trigger to the table and check inside if it is 'the row' that has been changed.
Another way is to only allow changes to...
October 27, 2003 at 8:40 am
This is a bit of a discussion that is driven by preferences of the DBA (or the developper).
Some reasons not to use bitmasks :
1. An integer column can only hold...
October 27, 2003 at 8:38 am
Viewing 15 posts - 31 through 45 (of 529 total)