Import UniData into SQL 2005

I have been trying to figure out how to get data from a UniData database into an SQL 2005 database to make building reports much easier. After installing the UniData ODBC tools from IBM I could not get the Import/Export wizard to connect to the ODBC.

After searching the Internet for the particulare errors I was getting I found the connection string should look like this. "Dsn=YOURDSN;Driver={IBM UniData ODBC DRIVER};uid=YOURUSER;pwd=YOURPASSWORD". As I found here http://www.bokebb.com/dev/english/2006/posts/2006108696.shtml.

Also you have to build you SELECT statements by hand, but that does not bother me as much as those other guys.

Update: 2-2-09
As of SQL 2005 SP3 this connection string no longer works in the Import/Export Wizard. Still looking into how to get it working again.

Howto: PC2724 Remote Management

If your like me one annoying issue is that the PC2724 management interface cannot be changed.  This can make it impossible to remotly manage the switch using the web interface if your using it with VLAN Trunks that will not carry VLAN1.  Example the Dell PC6248 L3 switch.  Effectivly the PC6248 VLAN1 is not routable so if your management VLAN is VLAN1 how can you manage it from a different VLAN?  You fool it!  This will work no matter what you use to do your intervlan routing.  We are using a pair of PC6248's.  I am not going to cover how to set those up.

1. Create your VLANs
   
   
   1. VLAN15 Phones
   
   
   2. VLAN20 PCs
   
   
   3. VLAN25 Management
   
   


2. Setup your uplink/trunk VLAN Membership
   
   
   1. VLAN15 Port 23+24 Tagged
   
   
   2. VLAN20 Port 23+24 Tagged
   
   
   3. VLAN25 Port 23+24 Tagged
   
   


3. Setup your uplink/trunk VLAN Port Settings
   
   
   1. Port 23+24 Admit Tag Only, PVID 1
   
   


4. Loop your management port to VLAN1
   
   
   1. Port 22 VLAN Membership 25 Untagged
   
   
   2. Port 22 VLAN Port Settings PVID 25
   
   
   3. Port 21 VLAN Membership 1 Untagged
   
   
   4. Port 21 VLAN Port Settings PVID 1
   
   


5. Connect Port 21, and 22 together.


6. Assign IP Addressing as if in VLAN25 for IP Address, Subnet, and Gateway.

Now you should be able to manage the device from any of your other VLANs. This assumes you already have your VLANs up, and InterVLAN routing working.