Enable Quoted Identifiers=0 System.Data.SqlClient.sqlConnection

Hi there,
this is probably a common question,
how can i include the "enabled Quoted Identifiers" settings in the
connection string of the sqlconnection.
on trawling through web pages i have identified
1 .that by default the quoted identifiers in SQL Server 2000 is by default
set to on
2. changing the status of quoted identifiers at the catalog level has no
affect at the connection level
since i have 1 global connection string
I would be grateful if anyone could help me in setting up this connection
stringHello,
As I know, you have to run SET QUOTED_IDENTIFIER { ON | OFF } via
connection and there is no such option to set this option in connection
string to SQL server.
Also, if you use odbc DSN to connect to SQL Server, you have the option to
configure this option in SQL Server DSN.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Enable Quoted Identifiers=0
System.Data.SqlClient.sqlConnection
>thread-index: AcZaMC8+PO+Q1I/hQvOGfgZaOBq/Mw==
>X-WBNR-Posting-Host: 83.141.82.45
>From: examnotes <cathiec@.newsgroups.nospam>
>Subject: Enable Quoted Identifiers=0 System.Data.SqlClient.sqlConnection
>Date: Fri, 7 Apr 2006 03:44:02 -0700
>Lines: 18
>Message-ID: <D8216A73-DDA7-417E-B53A-54889FDF94AF@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.connect
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:47316
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.connect
>Hi there,
>this is probably a common question,
>how can i include the "enabled Quoted Identifiers" settings in the
>connection string of the sqlconnection.
>on trawling through web pages i have identified
>1 .that by default the quoted identifiers in SQL Server 2000 is by default
>set to on
>2. changing the status of quoted identifiers at the catalog level has no
>affect at the connection level
>since i have 1 global connection string
>I would be grateful if anyone could help me in setting up this connection
>string
>
>

Enable Common Criteria Compliance

SQL 2005, SP2
In the Security section of the Server Properties dialog in SSMS, there is a
check option for "Enable Common Criteria Compliance". In the online help,
this position is listed as the "Allow Direct Updates to System Tables"
option that has been around for a while.
Does anyone know if the "Enable Common Criteria Compliance" is a one for one
replacement for the "Allow Direct Updates to System Tables" or does if have
different functionality? I did google and Microsoft web searches and
couldn't come up with any hits on the Enable Common Criteria option.
ThanksSorry for duplicate messages. I had an operator malfunction.
"Al" <zyck@.tconl.com> wrote in message
news:OhDQHm1VHHA.600@.TK2MSFTNGP05.phx.gbl...
> SQL 2005, SP2
> In the Security section of the Server Properties dialog in SSMS, there is
> a
> check option for "Enable Common Criteria Compliance". In the online help,
> this position is listed as the "Allow Direct Updates to System Tables"
> option that has been around for a while.
> Does anyone know if the "Enable Common Criteria Compliance" is a one for
> one
> replacement for the "Allow Direct Updates to System Tables" or does if
> have
> different functionality? I did google and Microsoft web searches and
> couldn't come up with any hits on the Enable Common Criteria option.
> Thanks
>
>|||Did you also update your Books Online (separate download)? I did, and search
ing for below gave me
three hits. It is *not* the same as the old "allow update", they probably on
ly re-used the BOL URL
(or similar).
Enable Common Criteria Compliance
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Al" <zyck@.tconl.com> wrote in message news:OhDQHm1VHHA.600@.TK2MSFTNGP05.phx.gbl...agreen">
> SQL 2005, SP2
> In the Security section of the Server Properties dialog in SSMS, there is
a
> check option for "Enable Common Criteria Compliance". In the online help,
> this position is listed as the "Allow Direct Updates to System Tables"
> option that has been around for a while.
> Does anyone know if the "Enable Common Criteria Compliance" is a one for o
ne
> replacement for the "Allow Direct Updates to System Tables" or does if hav
e
> different functionality? I did google and Microsoft web searches and
> couldn't come up with any hits on the Enable Common Criteria option.
> Thanks
>
>

Enable Common Criteria Compliance

SQL 2005, SP2
In the Security section of the Server Properties dialog in SSMS, there is a
check option for "Enable Common Criteria Compliance". In the online help,
this position is listed as the "Allow Direct Updates to System Tables"
option that has been around for a while.
Does anyone know if the "Enable Common Criteria Compliance" is a one for one
replacement for the "Allow Direct Updates to System Tables" or does if have
different functionality? I did google and Microsoft web searches and
couldn't come up with any hits on the Enable Common Criteria option.
Thanks
Sorry for duplicate messages. I had an operator malfunction.
"Al" <zyck@.tconl.com> wrote in message
news:OhDQHm1VHHA.600@.TK2MSFTNGP05.phx.gbl...
> SQL 2005, SP2
> In the Security section of the Server Properties dialog in SSMS, there is
> a
> check option for "Enable Common Criteria Compliance". In the online help,
> this position is listed as the "Allow Direct Updates to System Tables"
> option that has been around for a while.
> Does anyone know if the "Enable Common Criteria Compliance" is a one for
> one
> replacement for the "Allow Direct Updates to System Tables" or does if
> have
> different functionality? I did google and Microsoft web searches and
> couldn't come up with any hits on the Enable Common Criteria option.
> Thanks
>
>

Enable Common Criteria Compliance

SQL 2005, SP2
In the Security section of the Server Properties dialog in SSMS, there is a
check option for "Enable Common Criteria Compliance". In the online help,
this position is listed as the "Allow Direct Updates to System Tables"
option that has been around for a while.
Does anyone know if the "Enable Common Criteria Compliance" is a one for one
replacement for the "Allow Direct Updates to System Tables" or does if have
different functionality? I did google and Microsoft web searches and
couldn't come up with any hits on the Enable Common Criteria option.
ThanksSorry for duplicate messages. I had an operator malfunction.
"Al" <zyck@.tconl.com> wrote in message
news:OhDQHm1VHHA.600@.TK2MSFTNGP05.phx.gbl...
> SQL 2005, SP2
> In the Security section of the Server Properties dialog in SSMS, there is
> a
> check option for "Enable Common Criteria Compliance". In the online help,
> this position is listed as the "Allow Direct Updates to System Tables"
> option that has been around for a while.
> Does anyone know if the "Enable Common Criteria Compliance" is a one for
> one
> replacement for the "Allow Direct Updates to System Tables" or does if
> have
> different functionality? I did google and Microsoft web searches and
> couldn't come up with any hits on the Enable Common Criteria option.
> Thanks
>
>|||Did you also update your Books Online (separate download)? I did, and searching for below gave me
three hits. It is *not* the same as the old "allow update", they probably only re-used the BOL URL
(or similar).
Enable Common Criteria Compliance
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Al" <zyck@.tconl.com> wrote in message news:OhDQHm1VHHA.600@.TK2MSFTNGP05.phx.gbl...
> SQL 2005, SP2
> In the Security section of the Server Properties dialog in SSMS, there is a
> check option for "Enable Common Criteria Compliance". In the online help,
> this position is listed as the "Allow Direct Updates to System Tables"
> option that has been around for a while.
> Does anyone know if the "Enable Common Criteria Compliance" is a one for one
> replacement for the "Allow Direct Updates to System Tables" or does if have
> different functionality? I did google and Microsoft web searches and
> couldn't come up with any hits on the Enable Common Criteria option.
> Thanks
>
>