I would take a stab at the staging table. We currently run a process that receives over 1 million entries per day. The database is able to keep...

Could you use a view?

Table (

Field1,

Field2,

OrigPwd VARCHAR(20)

)

CREATE VIEW v_Table AS

SELECT Field1, Field2, '******' AS OrigPwd....

Guarddata-

You might try

INSERT INTO <table>

SELECT val1, val2, COUNT(*) FROM <table>

Guarddata-

I'm sure there are better descriptions of transaction handling, but I hope someone else known the reference. I was fortunate to have a couple of days to test different...

Sorry Lenard. Perhaps if we understood more of the background we could help find another solution. Sounds like you are pretty adept. Good Luck!

Guarddata-

Sorry Lenardd - I left out that part of the response . I was thinking you could use this in place of the function. Is...

That is correct - I ran into that problem also a while back (no sp_executesql inside a function). Kind of an obstacle.

Perhaps you can build the SQL like

'SELECT '...

You are correct about the Auto-Commit...but that applies to the entire procedure. In order to break it down we use the BEGIN and COMMIT.

Guarddata-

Actually, lenardd is on the right track with the OUTPUT handling in the sp_executesql. I have been able to use variables nicely with dynamic SQL.

The greater challenge in my...

Yes - if there is an index that matches the WHERE clause - everyone is happy.

The BEGIN and COMMIT are necessary. Without them the process runs in a single...

The way to tell if the script actually worked is to run it in Query Analyzer. You should see that the results returned indicate 290391 rows affected once, then...

buktseat, Interesting request to have all the output in a single field. I assume this is for display.

Ordinarily, I would have done

SELECT CaseID,

SUM( CASE StatisID WHEN 4...

Mind still not in gear this morning... JPipes - why do you say two indexes would be needed?

We have even had good success by using ROWCOUNT:

SET ROWCOUNT 10

SELECT * FROM...

One more thing to remember... when you use TOP #....ORDER BY the system must produce the entire result set anyway. Performance improves significantly when you can use an index...

In previous versions of MS-SQL, cursors were such poor performers than almost any other method would have been preferred. The last set of tests we ran on SQL 2000...