Temporary Tables in SQL 6.5 & IIS 4.0

Temporary Tables in SQL 6.5 & IIS 4.0

Post by Michae » Tue, 13 Jan 1998 04:00:00



Hi Gurus,

I am doing a query that requires me to put some results in a temporary
table.
The first query using IDC works fine, but if I use the back-button to repeat
the
query I get the following message:

Error Performing Query
[State=S0001][Error=2714][Microsoft][ODBC SQL Server Driver][SQL
Server]There is already an object named '#answers' in the database.

"#anwers" is the temporary table I create. ( see the whole query below).

This all worked fine under IIS 3.0, but after upgrading to IIS 4.0 we
experienced this
problem.

Any help appreciated,

Michael

IDC-query:

Datasource: Web SQL
SQLStatement:




+ SELECT * into #answers FROM isp WHERE areanumber like '%%%riktnr%%%' or
riks=1
+ if '%Erbjuder_Epost%' = 'Ja' delete from #answers where erbjuder_epost <>
'ja'
+ if '%egen_hemsida%' = 'Ja' delete from #answers where egen_hemsida <> 'ja'
+ if '%nyhetsgrupper%' = 'Ja' delete from #answers where nyhetsgrupper <>
'ja'
+ if '%stoder_cgi%' = 'Ja' delete from #answers where stoder_cgi <> 'ja'
+ if '%stoder_fp%' = 'Ja' delete from #answers where stoder_fp <> 'ja'
+ if '%modem_hastighet%' = '56.600 Bps' delete from #answers where
modem_hastighet <> '56.600 Bps'

kvallspris *60 /100) + manad  from #answers where riktnr like '%%%riktnr%%%'
or riks=1 order by totalkostnad asc
Template: find.htx
Username: xx
password: xxxxxx

 
 
 

Temporary Tables in SQL 6.5 & IIS 4.0

Post by Scott Nicho » Tue, 13 Jan 1998 04:00:00




Quote:> Hi Gurus,

> I am doing a query that requires me to put some results in a temporary
> table.
> The first query using IDC works fine, but if I use the back-button to
repeat
> the
> query I get the following message:

> Error Performing Query
> [State=S0001][Error=2714][Microsoft][ODBC SQL Server Driver][SQL
> Server]There is already an object named '#answers' in the database.

> "#anwers" is the temporary table I create. ( see the whole query below).

> This all worked fine under IIS 3.0, but after upgrading to IIS 4.0 we
> experienced this
> problem.

This *may* be the result of upgrading ODBC on the server.  The newest ODBC
driver manager supports connection pooling.  As such, it does not actually
close the connection when the client says close.  Instead, the connections
stay open for a configurable length of time before being closed.  When a
new open request comes in, the manager checks for an open but unused
connection first.  

Actually, it may be a registry setting rather than ODBC version per se.  In
KB Article ID: Q169470 you'll find the following

7. Q. How do I enable connection pooling for Active Server Pages (ASP) or
      ActiveX Data Objects (ADO)?

   A. Microsoft Internet Information server (IIS) version 3.0 with Active
      Server Pages takes advantage of connection pooling. You can enable
      connection pooling for IIS users by changing the value of
      StartConnectionPool to 1. The StartConnectionPool is located under
      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W3SVC\ASP
      \Parameters.

I take it from this that pooling is *not* enabled by default.  Perhaps with
IIS 4.0, it is.  I'd advise you to at least check this setting in the
registry.  If StartConnectionPool is 1, try setting it to 0, restarting
IIS, then see whether you get the old behavior.

Scott Nichol

 
 
 

Temporary Tables in SQL 6.5 & IIS 4.0

Post by Michae » Wed, 14 Jan 1998 04:00:00


Thanks for your help.
Unfortunately this is not the problem, I tried several different
combinations
without any luck.

If anybody else heard of this problem please let me know.




>> Hi Gurus,

>> I am doing a query that requires me to put some results in a temporary
>> table.
>> The first query using IDC works fine, but if I use the back-button to
>repeat
>> the
>> query I get the following message:

>> Error Performing Query
>> [State=S0001][Error=2714][Microsoft][ODBC SQL Server Driver][SQL
>> Server]There is already an object named '#answers' in the database.

>> "#anwers" is the temporary table I create. ( see the whole query below).

>> This all worked fine under IIS 3.0, but after upgrading to IIS 4.0 we
>> experienced this
>> problem.

>This *may* be the result of upgrading ODBC on the server.  The newest ODBC
>driver manager supports connection pooling.  As such, it does not actually
>close the connection when the client says close.  Instead, the connections
>stay open for a configurable length of time before being closed.  When a
>new open request comes in, the manager checks for an open but unused
>connection first.

>Actually, it may be a registry setting rather than ODBC version per se.  In
>KB Article ID: Q169470 you'll find the following

>7. Q. How do I enable connection pooling for Active Server Pages (ASP) or
>      ActiveX Data Objects (ADO)?

>   A. Microsoft Internet Information server (IIS) version 3.0 with Active
>      Server Pages takes advantage of connection pooling. You can enable
>      connection pooling for IIS users by changing the value of
>      StartConnectionPool to 1. The StartConnectionPool is located under
>      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W3SVC\ASP
>      \Parameters.

>I take it from this that pooling is *not* enabled by default.  Perhaps with
>IIS 4.0, it is.  I'd advise you to at least check this setting in the
>registry.  If StartConnectionPool is 1, try setting it to 0, restarting
>IIS, then see whether you get the old behavior.

>Scott Nichol

 
 
 

Temporary Tables in SQL 6.5 & IIS 4.0

Post by Michae » Wed, 14 Jan 1998 04:00:00


I found a solution.
It is actually quite easy, I just added

+ drop table #answers

to the last line in the IDC-script. This was not necessary under IIS 3.0 and
according to the SQL 6.5 docs it is not necessary.

Seems to be another undocumented feature of IIS 4.0.

/Michael

>Thanks for your help.
>Unfortunately this is not the problem, I tried several different
>combinations
>without any luck.

>If anybody else heard of this problem please let me know.




>>> Hi Gurus,

>>> I am doing a query that requires me to put some results in a temporary
>>> table.
>>> The first query using IDC works fine, but if I use the back-button to
>>repeat
>>> the
>>> query I get the following message:

>>> Error Performing Query
>>> [State=S0001][Error=2714][Microsoft][ODBC SQL Server Driver][SQL
>>> Server]There is already an object named '#answers' in the database.

 
 
 

1. Korean character garbaged in SQL 6.5 + IIS 4.0 + IE 4.01

Dears

  When I try to insert Korean character on MS-SQL 6.5 by using Internet
Explorer 4.01 with CGI, all Korean characters are garbaged. I tried to set
ODBC & MIME setting but it didn't work. FYI, my CGI is programmed in TCL
(Tool Command Language) 7.5. I'm wondering this problem is upto IIS or the
incompatibility of TCL with Korean character. Please let me know any idea!

2. Filemaker solution (Template) for Bug tracking in a software development company

3. SQL 6.5 and IIS 4.0 odbc timeout

4. US FL Tampa Bay Area - Visual FoxPro Programmer/Analyst position available

5. SQL 6.5 and IIS 4.0 ODBC timeout

6. Oracle 8i JDBC Problem

7. Indexing SQL 6.5 database for IIS 4.0

8. C-ISAM and Unix permissions

9. SQL 6.5 and IIS 4.0 Timeout

10. IIS 4.0/ODBC/SQL 6.5/ASP with ADO Security Problem

11. SQL 6.5 and IIS 4.0 ODBC timeout

12. IIS 2.0 V. 4.0 + ISAPI-DLL + MS SQL 6.5

13. postgreSQL db temporary on Microsoft IIS 4.0