| bio | website | |
|---|---|---|
| location | New York, NY | |
| age | 47 | |
| visits | member for | 2 years, 4 months |
| seen | 1 hour ago | |
| stats | profile views | 35 |
25 years in the field
ASM, C, C++, C#, VB, ASP.NET, TSQL +many more
Programmer, Architect, Team Lead, Director, CTO
MS Comp. Sci @ NYU '95
Contact: hoganlong at gmail.com
(Will code for work)
ASM, C, C++, C#, VB, ASP.NET, TSQL +many more
Programmer, Architect, Team Lead, Director, CTO
MS Comp. Sci @ NYU '95
Contact: hoganlong at gmail.com
(Will code for work)
|
1d |
awarded | Caucus |
|
1d |
awarded | Constituent |
|
Sep 20 |
awarded | Popular Question |
|
Jul 26 |
awarded | Yearling |
|
Jul 26 |
answered | Ordering of rows with different kinds of objects |
|
Jul 26 |
answered | Single query sending and retreiving duplicate data on MS SQL Server? |
|
Jul 26 |
comment |
Ordering of rows with different kinds of objects Would you ever be selecting more than one object type at the same time? |
|
Feb 17 |
awarded | Critic |
|
Feb 17 |
awarded | Citizen Patrol |
|
Feb 17 |
comment |
Same restore file (.bak), huge difference of execution duration time on various computers -1 : No need for cursing. |
|
Jun 21 |
comment |
Emulate a TSQL sequence via a stored procedure @dportas - My mistake, I was under the wrong impression, I won't ask any more questions on dba.stackexchange.com |
|
Jun 20 |
comment |
Emulate a TSQL sequence via a stored procedure @dportas - Ah very good, I didn't know Identity insert did that. So consider this: A runs the first two lines, B runs 4 lines; now identity insert is off. A runs and inserts 50. A and B run to completion with values 50 and 51. |
|
Jun 19 |
awarded | Scholar |
|
Jun 19 |
accepted | Emulate a TSQL sequence via a stored procedure |
|
Jun 16 |
awarded | Commentator |
|
Jun 16 |
comment |
Emulate a TSQL sequence via a stored procedure @dportas -- Let me try and be clearer -- my question is this; If this is run in a multi-client environment and the SP is called at the same time with two clients A w/ param 50 and B w/ param 500, B runs the first 4 lines first (setting ID to 500), then A runs the first 4 lines (setting ID to 50), then B finishes the last 3 lines (getting a result of 51) and then A finishes (getting a result of 52). This does not meet the requirements -- B returned a result less than 500. Correct results would be (A=51, B=501) or (A=502, B=501) |
|
Jun 14 |
comment |
Emulate a TSQL sequence via a stored procedure @dportas - I'm not saying I was able to create such a scenario, just that it is possible with the code you posted. |
|
Jun 14 |
comment |
Emulate a TSQL sequence via a stored procedure @dportas - A called with inID of 500, B called with inID of 50 -- action - A returns with 51, B with 52. Requirement fail. |
|
Jun 14 |
comment |
Emulate a TSQL sequence via a stored procedure +1 for the MS links and OUTPUT point. (Sadly the MS links don't seem to apply 100%). |
|
Jun 14 |
comment |
Emulate a TSQL sequence via a stored procedure +1 for SET XACT_ABORT |