quote:
When one customer is modifying their extended table, would we see locking issues on the primary table for customers other than the one modifying the extended table?
No, SQL Server implements row-level lock. Looking at your keys, I don't believe this would be an issue.
quote:
Also, this would mean that all my select statements would need to be dynamic in that they would be joining different extended tables based on the customer. Would it be worth it to make one primary stored procedure that dynamically called a second stored procedure based on the customer doing the select? This way I would not get real optimization on the first sp but would on the secondary SP?
Good point, and yes, it would be worth your while.
Good luck with your solution; I realize this type of solution can be tricky! 🙂
Jay