You are a developer hooked on the IBM® DB2® Universal Database (DB2 UDB) system. You love the integration of DB2 UDB with .NET in the Microsoft Visual Studio .NET environment. You like to play around with code and databases so you have an instance that you use for development, and an instance that you use for experimentation. You have one problem: the IBM Explorer in Visual Studio .NET only shows the default instance (typically DB2) when it starts up on a typical workstation.
In this article, I'll show you the simplest, yet most often overlooked, way to quickly work with a test database that resides in another instance when using the Visual Studio .NET tool set to develop DB2 UDB applications. This method gets a whole lot easier in the up-and-coming Stinger release in which cataloging remote databases (even ones that reside in remote instances) can be performed within the tooling. For now, the only other way to accomplish what I am going to show you is by cataloging the database and performing an instance attach. This requires working with the database catalogs, and that is just something that we don't feel like learning, right?
The article continues at