GregStevens wrote: Any thoughts would be very much appreciated I think you should take measurements, and note down the version of the database that you tested. GregStevens wrote: Which one of these will be faster to perform queries on? I'm hoping Sqlite, since it could be a fast implementation in native code without much overhead. GregStevens wrote: My intuition is that the second will be slower because it is a transaction on a non-local database, but I don't know this for sure. How about putting it one the same machine? You also could consider Times Ten[^] from Oracle. GregStevens wrote: When the table is in-memory, which computer's memory is it actually in? That depends on the specific implementation; most of the time it will be in memory that's managed by Windows, putting it into the virtual memory area. Others might have optimizations. GregStevens wrote: How much volume would have to be going on for a difference to actually be noticable? You can review the amount of free memory using the Task Manager; Your computers fysical memory - used memory = free memory Once the system starts to page out memory, you'll notice delays. That can range from minimal delays (say, served from the 64Mb buffer of memory in your harddisk) to large delays (Windows reshuffling a lot on disk, paging in and out other applications that are also running, your computer nearly grinding to a halt) Bastard Programmer from Hell :suss:

Thanks for the suggestion! I've done it, and the article is now posted. Cheers! --Greg

Hmm.... I'm not sure you understand. I'm still trying to make use of a class name in the external assembly, but I'm trying to make use of it in a code-behind page, rather than a compiled class. Specifically, I have installed an external assembly called SimpleChart, which gives me a file called SimpleChart4.dll. Then, in a code-behind page I say: Imports SimpleChart4 which is the name of the namespace, and is the line used in all of their example code. However, it gives me an error, telling me that it doesn't recognize the type. In theory, if I had the Visual Studio.NET application, I could click on "Add Reference", choose the "COM" tab, and add a reference to the DLL, and then suddenly it should be able to recognize the SimpleChart4 namespace/type. However, since I do not use the Visual Studio.NET application, I'm wondering how to do this without.... ----Greg

Thank you so much!

Thank you! This worked perfectly.

Well, that isn't right, because the crux of the problem is I'm working within the code-behind page of a user control, not the main page. As a result, I don't have direct accss to con2 or con1 as properties. So I can't use, for example "con1.drop1.SelectedItem", because it will say "con1 not defined". And if I try something like "Page.con1.drop1.SelectedItem" it will say that con1 is not a property of Page. I actually found my answer, though, just FYI: I needed to use the Page.FindControl() method, which solved my problem.

Always use ANSCII standards for writing queries this means even joins, instead of where clause condition first join the table and put where clause for specific requirement. Regards, Jaiprakash M Bankolli jaiprakash.bankolli@gmail.com

You don't mention what version of Oracle you're using, but the newer versions (9i and 10g, for sure... I think 8i) have built-in SQL extensions for dealing with hierarchical data. If you were to take advantage of them, it looks as if you may be able to reduce your processing down to a single query. Here are a couple of resources to get started with: Querying Hierarchical Data with CONNECT BY[^] Oracle Database SQL Reference (10g) - Hierarchical Queries[^] Just SQL Part VII - Hierarchical Queries[^] You may also wish to consider using the System.Data.OracleClient[^] for your connectivity, rather then using raw OleDB. The backing technology is the same, but the Oracle Client has been optimized for Oracle. Oracle also provides its own Oracle Data Provider for .NET[^], if you are more comfortable with that. Finally, for performance and security reasons, you may wish to consider moving your query into the database as a stored procedure. This will allow the DBMS to compile and cache the execution plan for your query, rather then having to figure it out each time you execute the SQL. Hope that helps. :) --Jesse "... the internet's just a big porn library with some useful articles stuck in