I have scripted my whole database and one of the parts that is installed in
two different database applications is the
ASP.NET Membership schemas. These
schemas come delivered as 4 or 5 SQL files. Let us call this "Membership
Schema". These are files delivered by Microsoft as part of the
ASP.NET
membership system. Both projects are based on Microsoft SQL Server 2005
(standard edition, not the express version). In both database projects the
ANSI_PADDING option is disabled.
Both of my projects use SQLCMD to run a "master script" that sequences all
the other 'child' SQL scripts including the 4-5 files mentioned above. In
project A the Membership Schema passes through the installation without any
problems.
I copied the same 4-5 files into Project B but when I run the script then
the very first SQL file of the Membership Schema using the standard
Microsoft SQL Server SQLCMD tool I get:
--> Starting execution of InstallCommon.SQL
Msg 102, Level 15, State 4, Server TLXDEV011, Line 1
Incorrect syntax near 'ANSI_PADDING'.
The only place in the InstallCommon.SQL (the first of the 4-5) where
ANSI_PADDING is mentioned is at the beginning:
/**********************************************************************/
/* InstallCommon.SQL */
/* ...
