> More likely when you installed SQL 2k, it installed itself as > a named instance, and possibly on a different port. Make > sure that you connect using the proper port, and proper instance > name.
Instance names are irrelevant to JDBC connections - it's all about the ports. But in any case, the original poster said he'd uninstalled SQL Server 2005. If he then installed SQL Server 2000 using the default configuration options, it would install a default instance and would use the default port (TCP/1433). If he didn't use the default configuration options, he would have to know which port to connect to, in order to verify datasource connectivity, because the SQL Server 2005 listener would no longer be installed. So, if he did in fact uninstall SQL Server 2005, your suggestion is unlikely to be the cause of his current problem. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:252002 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
