Same app for multiple clients and custom stored procedures in SQL Server
<p>We have the same app source (with some custom "if x client then") and basically the same SQL Server database structure. But, some clients need slightly different stored procedures.</p>

<p>What would be best practice in this scenario for long term maintaining the databases and keeping the correct structure? As of now, for example when I change the procedure in one database and need to do the same in 9/10 others I just ALTER procedure and USE different database. But, I can't keep track of which procedures are different in that special snowflake client.</p>

<p>Any ideas? The plan is of course to get more clients so that's looking for trouble.</p>

<p>I try to push the "one fits all" concept but hey, what can you do...</p>

<p>Maybe have that "if x client then" as case statement in a SQL Server stored procedure and then you can just ALTER mindlessly?</p>