|
|
Posted by crazyone on 10/02/06 14:59
Hi all,
We recently started to receive complaints about our install project not
working and giving and shitload of error messages related to SQL. We
later found out that the problem was the users we were trying to bind
to we're not created because of the domain password policy feature
implemented into SQL Server 2005.
After much dabbling around the SQL scripts that created the database
structure, we came to the conclusion that only this piece of code could
correct our problem :
CREATE LOGIN mynewuser WITH PASSWORD = '', CHECK_POLICY = OFF,
CHECK_EXPIRATION = OFF
This runs perfectly fine on SQL2005, but not on SQL2000. We have been
searching for a way to have code in SQL files executed on install that
doesn't fail to compile when run against the server and that will
bypass the password policy in case it's a SQL Server 2005...
Right now we are testing a feature available in MSI that can filter
scripts not matching a database version, but the problem with this, is
that we are missing a lot of features that InstallShield has. In short,
we need Help to fix this issue and be able to continue with
development.
In hopes to receive a a prompt anwser
Navigation:
[Reply to this message]
|