Is anyone using Windows Authentication with versioning? The problem I am having with it is that I cannot find a way to create the new versions nightly during my compress process. The best option I have come up with so far is to use an ArcObjects script that creates the version for each user when they log in by adding it to their Active Directory login script. I would appreciate any other ideas that may be out there that would allow me to keep the fully automated versioning process but with the advantages of Windows Authenticated users.
Based on the advice from Teresa Villena I was able to find a way to solve this issue. Here is the T-SQL code I am using to create each version in case it will help someone else. This creates a private version.
exec sde.create_version 'sde.Default', '{VersionName}', 2, 0 , 'Owners Version';
update data.sde.SDE_versions
set owner = '"{Domain}\{User}"'
where name = '{VersionName}'
The rest of the versioning process must still be done in python to Reconcile, Post and Delete versions followed by killing connections and compressing the states. Does anyone know of a way to compress the states other than a custom script that moves the edits from the delta tables to the base tables?