Permanently running, but does it actually hold a lock on the file permanently? That's what you need to check. If you double-click on the file and it opens,...

Definitely, which is why I suggested the retries on the job. Do you have any figures on how long the application takes to transfer the data into the CSV...

Sounds like you attempted the import at the very moment the CSV file was being written to by the third-party program. Try creating an SSIS package and running it...

Another way to do it is to create a RehireCode table with (1,A), (2,B), ... , (27,AA), (28, AB), ... and join to that.

27 is an awful lot of times...

According to Books Online, with ALTER INDEX...REORGANIZE, "long-term blocking table locks are not held and queries or updates to the underlying table can continue during the ALTER INDEX REORGANIZE transaction"....

More than 1 what? According to the e-mail, what was the blocking query, and what was the blocked query?

John

Ivan Mohapatra (9/30/2013)

---

well gila i have the details of which all others query was running @ that point of time but alter index reorganize is the head of the blocking...

Yes, but how do you know it's the ALTER INDEX...REORGANIZE statement that's doing the blocking? The code you posted does more than that.

How long does the blocking have to...

What is a blocking email and under what circumstances do you get one? Have you managed to ascertain which particular statement is causing the blocking?

John

I don't know why that would hold a lock for a long period of time. Have you tried to use sys.dm_os_waiting_tasks to see which session is doing the blocking?

John

Rebuilding indexes will take locks; reorganising won't. Please will you post your code?

John

Chinna

You need to REVERSE the string and then look for the first space after the "@".

John

Sounds as if your database is in single user mode.

SELECT user_access_desc

FROM master.sys.databases

WHERE name = '****'

John

Do you think so? The warning messages occur at run time,...

OK, so you have a staging database and a live database, right? And one of those procs runs to "tidy up" the staging database before the other one runs...