Viewing 15 posts - 196 through 210 (of 252 total)
I did not read all the responses - so many! However, I don't think concurrency was mentioned. Placing a clustered index on an identity column places new inserts...
RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉
November 10, 2003 at 8:43 am
In the update trigger, use the inserted and updated "tables" to compare the record values before and after - they might not actually change. An identity id is handy...
RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉
October 28, 2003 at 9:43 am
How about both? Use a bit mask and add a computed column for the answer to each question.
RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉
October 28, 2003 at 9:20 am
My understanding is, and this might be wrong, is that you must create the table first before using the "INSERT #table Execute proc". A "SELECT ... INTO #temp ..."...
RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉
October 28, 2003 at 9:06 am
Normally, the best performance is obtained from SQL Server if you can use a set based query. A cursor or a loop should be a last resort unless the...
RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉
October 28, 2003 at 8:44 am
For this reason, I would also avoid xp_sendmail in SQL Server jobs. I've seen such a hang prevent scheduled jobs from executing. There are other options. I...
RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉
October 28, 2003 at 8:18 am
The debugger interface is required on the client.
RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉
October 23, 2003 at 9:40 am
quote:
quote:
I like to put the drop in myself. Sometimes to debug a procedure,...
RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉
October 23, 2003 at 9:28 am
If you are talking about the SQL Server Error logs, try looking up "Using Startup options" in BOL. There should be an -e parameter specifying the path to the...
RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉
October 21, 2003 at 1:33 pm
Is a SET NOCOUNT ON required while processing the temp table?
RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉
October 21, 2003 at 1:07 pm
quote:
...the upgrade changes the -- by removing it....
This sounds like a serious bug to me....
RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉
October 17, 2003 at 8:39 am
On advantage of using a job step is that the step history will contain information from prints or raiserrors. Comes in handy. Good luck in finding this output...
RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉
October 17, 2003 at 8:27 am
I have found that using a join normally produces a faster query.
SELECT t1.*
FROM #temp1 t1
LEFT JOIN #temp2 t2
ON t2.ID = t1.ID
WHERE t2.ID IS NULL
RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉
October 16, 2003 at 9:41 am
I would also make sure that your public roles do not have object permissions.
RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉
October 16, 2003 at 9:34 am
The conversion might be tricky. In the old style, the where clause is applied before the join while in the new style the where is applied after the join....
RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉
October 16, 2003 at 8:55 am
Viewing 15 posts - 196 through 210 (of 252 total)