> Ok.. grrr... here's an interesting question for the SQL DBA > Guru Gods (and Goddesses). The client is on a shared host. > Dedicated web server, but shared SQL server - we only have one > DB to play with. Can I create an ODBC source for the client > storage only, while still using OLEDB for the rest of the > site, or will this cause problems with the system tables, etc?
You should be able to do this without any problem. Personally, though, I'd probably just set up an ODBC data source and use that for everything - I haven't seen any consistent advantage with OLEDB over ODBC. > I know you should never define multiple ODBC or OLEDB sources > for accessing/manipulating the same tables. I haven't heard this, myself. I can't see what harm it would do, although you obviously would have more database connection overhead - you'd have two pools of connections, rather than one. However, having two ODBC data sources isn't much different from having two users of the database with separate user accounts, from the perspective of the database. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusiona FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
