This is a discussion on SBS 2003 SQL 2005 within the SQL Server Data Warehousing forums, part of the Microsoft SQL Server category; --> Hello I have 2 networks network A and B both networks are running SBS 2003. On Network A I ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello I have 2 networks network A and B both networks are running SBS 2003. On Network A I have installed SQL 2005 On Network B I have Yardi SQL Both the networks are being controlled by SBS 2003. What I would like to do is have the SQL 2005 server communitcate with Yardi SQL Server. I have tried using naming piping but when I attempt to setup OCDB the SQL 2005 can't communicate with the Yardi SQL and vice versa. I have also tried vpn with the same problem. Is it possible for SQL 2005 to communicate with Yardi SQL ? |
| ||||
| The Guy wrote: > *Hello > > I have 2 networks network A and B both networks are running SBS > 2003. > On Network A I have installed SQL 2005 > On Network B I have Yardi SQL > > Both the networks are being controlled by SBS 2003. What I would > like to do > is have the SQL 2005 server communitcate with Yardi SQL Server. I > have > tried using naming piping but when I attempt to setup OCDB the SQL > 2005 can't > communicate with the Yardi SQL and vice versa. I have also tried vpn > with > the same problem. Is it possible for SQL 2005 to communicate with > Yardi SQL > ? * Sure it's possible. As long as you have the right ODBC/OLEDB driver and you have the proper ports/routes opened up between both servers. -- arbert ------------------------------------------------------------------------ Posted via http://www.codecomments.com ------------------------------------------------------------------------ |