With this type of configuration, the Spotfire database will use Windows accounts for authentication. The current user who is running the scripts to create the database must have administrative privileges on the database server, but the Spotfire process should run as a different user when connecting at runtime. Therefore, the scripts have been designed to set up the database using a different Windows account than the one the Spotfire Server will use to access the database. This user is assigned to the variable WINDOWS_LOGIN_ACCOUNT. Note that the user who runs the scripts to create the database will get database owner permissions (dbo) to the database and will be able to administer the Spotfire database using integrated authentication.

If the user assigned to the WINDOWS_LOGIN_ACCOUNT variable already exists as a login on the database server, the create_server_user_ia.sql script must be edited. The following rows should then be commented out:

use master 
GO 
CREATE LOGIN [$(WINDOWS_LOGIN_ACCOUNT)] FROM WINDOWS WITH 
DEFAULT_DATABASE=[$(SPOTFIREDB_DBNAME)],DEFAULT_LANGUAGE=[us_english] 
GO 
ALTER LOGIN [$(WINDOWS_LOGIN_ACCOUNT)] ENABLE 
GO 
DENY VIEW ANY DATABASE 
TO [$(WINDOWS_LOGIN_ACCOUNT)]

As mentioned above, for security reasons, the Spotfire server process should connect as a different user than the user that runs this script. If you really want to use the same account then you must comment out the following lines from create_server_user_ia.sql:

CREATE USER [$(SPOTFIREDB_USERNAME)] FOR LOGIN [$(WINDOWS_LOGIN_ACCOUNT)]
GO