Our DBA is having problems running maintenance tasks on the SQL Server instance Vault is installed to and wants to switch the QUOTED_IDENTIFIER setting off for sgvault. Can anybody think of any problems doing this might cause?
We're running Vault 3.0.7 on Windows 2003.
Thanks.
QUOTED_IDENTIFIER setting on Vault DB
Moderator: SourceGear
The Vault schema uses computed columns in an index. This requires:
These options set to ON: ANSI_NULLS, ANSI_PADDING, ANSI_WARNINGS, ARITHABORT, CONCAT_NULL_YIELDS_NULL, QUOTED_IDENTIFIER
This option set to OFF: NUMERIC_ROUNDABORT
--------
Instead of the using the Maint Plan extended stored procedure, you can use the alternate DBCC commands instead. See Maintenance: Vault/Dragnet database(s) for more information.
These options set to ON: ANSI_NULLS, ANSI_PADDING, ANSI_WARNINGS, ARITHABORT, CONCAT_NULL_YIELDS_NULL, QUOTED_IDENTIFIER
This option set to OFF: NUMERIC_ROUNDABORT
--------
Instead of the using the Maint Plan extended stored procedure, you can use the alternate DBCC commands instead. See Maintenance: Vault/Dragnet database(s) for more information.
Jeff Clausius
SourceGear
SourceGear
Note that in SQL Server 2000 SP4 there is a new flag that can be added to an existing maintenance plan "integrity checks" or "optimizations" job step that will eliminate this error (-SupportComputedColumn). We were having this same problem, and this fixed it without requiring a separate maint plan as described above.
http://support.microsoft.com/kb/902388/
Greg Gonzalez
sqlSentry
http://support.microsoft.com/kb/902388/
Greg Gonzalez
sqlSentry
Last edited by ggonzalez on Fri Feb 10, 2006 10:44 am, edited 1 time in total.