i thought avoiding the use of 1433 was to avoid brute force attacks to discover passwords....script kiddies or worse.

it looks like your procedure is recursively calling itself, correct? you might be hitting the max number of nesting levels or something;

I'm not sure what the proc is doing exactly...

dioscoredes (3/25/2011)

---

==>>what is the proc doing?

inserting a single row into a small table repeated

maybe 100 times. The proc quits silently after say 20

inserts. Tinkering shows any DML causes the premature...

what is the proc doing? if the proc is accessing anything outside of the database, it might be stopping/erroring due to permissions..you mentiond something about sqlcmd to fix stuff;

maybe when...

ok, here's a crappy example schema i slapped together, just as an example.

if you step thru to the end, you'll see that the view at the end will always have...

SQL handles concurrency very well and automatically; it automatically locks a row of data for the milliseconds it takes to update the row, releasing the row as soon as the...

And if the database is read only, you'll have to change it, change the collation, then change it back to read only again

Right click Dtabase....Properties

Select "Options" and scroll to the...

malleswarareddy_m (3/24/2011)

---

You guessed correct .I need a recursive cte but am getting dependencies using dynamic management function.

but it is not supporting to write the code for recursive ctes .

for example...

maybe thinking outside of the box can help;

show us the original working query, and explain what you wanted to do that spawned the query you posted; might be a simpler...

ok if it is a datetime, isn't this selecting a date that is between , say...

well, as an example of the OR, something like this might help...the three queries might be faster seperately than together...you'd have to test:

SELECT [STUFF] FROM [...]

WHERE (dbo.Notes.Completed = 0)...

looking again, it looks like you have some fields that are varchar, but storing dates in them, hence your conversions.

can you convert the columns to real datetime fields instead?

if not,...

well, i can point to a few things that you might take under consideration:

If you use LIKE '%..., it's a guaranteed table scan...that means every rows gotta be analyzed. that...

at a glance? you should replace the queries with TWO CTE's

you are joining the same tables over and over again (search for "_1" int e statement provided for examples)

as...

the # levels returned by any of our queries for hierarchys above can be more than the number of actual queries needed to delete from a parent table....it's very...