Re: Utilizing temporary tables via an ODBC connection?
Posted in 2005
Topics: Performance & Tuning, Connectivity: ODBC / JDBC / .NET, Server Administration
"William Fields" <Bill_Fields@azb.uscourts.gov> wrote in message news:d0a06v$54p$1@apollo.nyed.circ2.dcn... > Thanks for the response, we've chosen not to make any server side mods, so > adding views or SP's is not in the gameplan. > > I was hoping I would be able to create/use temp tables via SQL over the ODBC > connection instead. > Well you could certainly do the job using ADO by building a recordset and populating and amending it as required. I also know that it's not always possible to amend the server side if it's a package (we run baan/informix - we don't muck about with the informix side, all the reporting's SQLServer based). But - if it's at all possible the server side option's the best IMHO. If not - just build a disconnected recordset - or recordsets using ADO and use a stepthrough. Performance is going to be horrible though - worst of both worlds. Using step through rather than set based code against an RDBMS - then exicuting it on the client side - with all the network traffic required? I'm sorry - I don't know your environment, but if necessary - drop the data to a reporting database, do it on that. However - I can't really do anything more than blunder about in the dark unless you actually give more specific information on what you're actually trying to do. I'm VB, SQLserver, Informix DBA and have used XBase (clipper, dbase) - which seems to cover most of the bases - and have not the faintest idea what I'm trying to help you do. I appreciate that that what you're doing is terribly sensitive but can you give slightly nore on what you're trying to do?
Thanks for the feedback Andrew. Nothing too terribly interesting, I'm just relaying some questions I've heard from my partner regarding taking existing recordsets and joining them within new SQL statements. Had another response suggesting the use of SQLExec() to tell the server to create a temp table, which just might work for our purposes.... Regards, -- William Fields MCSD - Microsoft Visual FoxPro US Bankruptcy Court Phoenix, AZ "I have no special talents, I am only passionately curious" - Albert Einstein "Andrew" <a@a.co.uk> wrote in message news:%htWd.4715$4x2.1215@newsfe4-gui.ntli.net... > > "William Fields" <Bill_Fields@azb.uscourts.gov> wrote in message > news:d0a06v$54p$1@apollo.nyed.circ2.dcn... >> Thanks for the response, we've chosen not to make any server side mods, >> so >> adding views or SP's is not in the gameplan. >> >> I was hoping I would be able to create/use temp tables via SQL over the > ODBC >> connection instead. >> > Well you could certainly do the job using ADO by building a recordset and > populating and amending it as required. I also know that it's not always > possible to amend the server side if it's a package (we run > baan/informix - > we don't muck about with the informix side, all the reporting's SQLServer > based). But - if it's at all possible the server side option's the best > IMHO. If not - just build a disconnected recordset - or recordsets using > ADO and use a stepthrough. Performance is going to be horrible though - > worst of both worlds. Using step through rather than set based code > against > an RDBMS - then exicuting it on the client side - with all the network > traffic required? I'm sorry - I don't know your environment, but if > necessary - drop the data to a reporting database, do it on that. > However - I can't really do anything more than blunder about in the dark > unless you actually give more specific information on what you're actually > trying to do. I'm VB, SQLserver, Informix DBA and have used XBase > (clipper, > dbase) - which seems to cover most of the bases - and have not the > faintest > idea what I'm trying to help you do. > I appreciate that that what you're doing is terribly sensitive but can > you > give slightly nore on what you're trying to do? > >