Ask a Question related to ASP Database, Design and Development.
-
Roger Withnell #1
Performance considerations accessing several database tables
I am using SQL Server, ASP and VBScript. My NavBar is built from database tables depending on browser's security status. Different tables are accessed at six times to do this on every page. Is it best to leave the recordset open throughout the page and use the data as required; put the data into arrays on the first access and then close the recordset; or put the data into session variables and only access the tables where necessary once in a session
Roger Withnell Guest
-
Accessing duplicate field names from different tables
Hi, I am joining two tables, and the two tables have the same field names, but they represent different data. eg. table 1 - People name -... -
Performance with linked tables
I notice that performance drops when using linked tables in two Access 97 databases instead of all tables in one database. I.e. the ASP page takes... -
Accessing Temp Tables
Hello Graham, You could try using global temp tables with a "##", in your case it would be - ##UserAccess. K "Graz79"... -
Joining Tables from different DBs => Do I have to care about performance?
Hi, I have a more theoretic question: I have two huge tables (db1.dbo.table1 and db2.dbo.table2). I need to join them. Will the effort to join... -
Accessing 2 tables with 1 name
I have 2 IDENTICAL tables (TableName_A and TableName_B) that I use in my production system. I have a table (TableState) with 1 row and 1 column... -
Brandon Ludwig #2 Re: Performance considerations accessing several database tables
I would put the data into arrays and close the recordset as soon as
possible.
Brandon
"Roger Withnell" <anonymous@discussions.microsoft.com> wrote in message
news:2665B9FB-1D89-4109-A439-4B9F588764CA@microsoft.com...tables depending on browser's security status. Different tables are> I am using SQL Server, ASP and VBScript. My NavBar is built from database
accessed at six times to do this on every page. Is it best to leave the
recordset open throughout the page and use the data as required; put the
data into arrays on the first access and then close the recordset; or put
the data into session variables and only access the tables where necessary
once in a session?>
>
Brandon Ludwig Guest
Reply With QuoteSimilar Questions and Discussions
Posting Permissions
- You may not post new threads
- You may post replies
- You may not post attachments
- You may not edit your posts
