Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Setting options is isql

Author  Topic 

na2173
Starting Member

38 Posts

Posted - 2003-09-26 : 13:27:21
Does any body know how to set ANSI NULLS ON AND SET QUOTED IDENTIFIER ON When ever i run the isql.exe , instead of setting this options in each .sql file, i just want to set this options globally

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-09-26 : 13:34:01
Go to Tools, Options, then Connection properties.

Tara
Go to Top of Page

na2173
Starting Member

38 Posts

Posted - 2003-09-26 : 13:38:53
That is you are running isqlw (Query analyzer), but if you are running a batch file isql.exe is there a way i can set up using some swithches
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-09-26 : 13:43:39
You can set this up at the database level. In EM, go to your database, right click go to properties, then options.

Tara
Go to Top of Page

na2173
Starting Member

38 Posts

Posted - 2003-09-26 : 13:51:07
The thing i am i asking the question, we use index views, and every time we run a script to update the tables we get an error on SET ANSI NULLS AND SET Quoted identifier off. We have already set up those options on the database level. Until unless i don't specify SET ANSIN NULLS AND SET Quoted idenfier on in .sql file, the script errors out, this only happens if i update the tables that participate in index views, Sometime we accidentaly forget to add those options in .sql file and the only time we come to know is that when we do a release to the staging box. because on the development box we run the scripts individually through query analyzer.

Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-09-26 : 13:59:49
Yes you will need to include those SET options every time you modify the tables. There is no way around this.

If you run the scripts in Query Analyzer in development, then how comes the error isn't noticed there?

Tara
Go to Top of Page
   

- Advertisement -