As an update:

All the administrative functions that were down are now back up. Spent the w/e researching and repairing. In the end it took a hotfix from M$...

And down the rabbit hole we go. I am not able access LSP, GPE, SQL Server Config Mgr, etc. I have confirmed that others are getting the same...

Unique identity on the source table will be a moot point once the testing table is populated. I would need to get time with the analysts to determine uniqueness...

John,

My question was for on-going iterative loads. Whether it would be possible to determine a tipping point for the overall scheme once all my changes are implemented. My...

I'm at 63 M and climbing. I'll tell you what though I'm definitely going to back this db up once I get past this initial load. If I...

I have the same suspicions you do Jeffery about the functions I had to add to get this to "work" causing the locking. I have gone back to my...

Oh and the answer to your last question is no. I think I would polish my resume up if that were the case. Not sure I shouldn't as...

I would run the package from my local machine if I went that route.

I had two batches in successfully and 3/4 through the 3rd the lead architect decided she would...

I was able to check QA and PROD just to ensure some trickery hadn't occurred in DEV that I wasn't aware of. There is nothing identified that uniquely id's...

EncounterId is not unique as there can be several charges against a single encounter.

Thank you all for your help.

The PRIMARY filegroup is set to Autogrow by 10 GB unrestricted on a drive with 770 GB free space remaining. The source DB PRIMARY...

MSDN's answer? "Take the highest session id, and terminate it using the KILL command." 😉

More info

EXEC sp_configure:

locks ...

So here is what I set up:

USE [myDB];

DECLARE @LoopCounter int

DECLARE @LoopCounterLoop int

DECLARE @LoopCounterMAX int

SET @LoopCounter = 1

SET @LoopCounterLoop = @LoopCounter + 5000000

SET @LoopCounterMAX = (SELECT COUNT(1) FROM OgDB.Fact.ChargeDetail)

WHILE @LoopCounter <=...

Just as an FYI I found that error in case anyone else comes searching for a similar issue.

Msg 9002, Level 17, State 4, Line 3

The transaction log for database '[databasename]'...

Ahh okay. I must have missed one. The db is already in SIMPLE mode. I just got used to wrapping everything in a transaction.

I will work on...