Second copy of Accounting Data (was RE: (RADIATOR) Connecting to MS SQL 2000)

[Jamz at AirNet.Com.AU]

Hugh and List,
	I have resorted to running Radiator locally on the SQL 2000 Server
with ActiveState Perl and DBI::ODBC.

Works very well! - and not surprisingly the database access is fast :)

Our existing Radiator server is running on a linux box and talking to a
PostgreSQL database on another machine, but we eventually want to move over
to the new server.

We have our new database structure in place but to begin the software
development cycle it would be really great to have a second copy of all the
accounting records flowing into the SQL 2000 database as well as our
exisiting PostgreSQL database.

Is there anything I can do to the Radiator config on the production machine
to get it to forward a copy of all the accounting radius packets to the
second server?

Cheers,
	Jamz.

> -----Original Message-----
> From: Hugh Irvine [mailto:hugh at open.com.au]
> Sent: Wednesday, 29 August 2001 11:55 AM
> To: Jamz at AirNet.Com.AU; radiator at open.com.au
> Subject: Re: (RADIATOR) Connecting to MS SQL 2000
> Importance: Low
> 
> 
> Hello Jamz -
> 
> I personally have had the most success with the free version of Sybase for
> Linux (www.sybase.com) with DBI:Sybase, and configure the Sybase client to
> connect to the MSSQL host. Alternatively, you can install a copy of
Radiator
> on W2000k using DBI:ODBC and then proxy from Radiator on the Linux host to
> Radiator on the W2000k host.
> 
> hth
> 
> Hugh
> 
> 
> On Wednesday 29 August 2001 12:05, Jamz at AirNet.Com.AU wrote:
> 
> > > Hi,
> >             We have been using Radiator on Linux for a while now,
> > connecting to a PostgreSQL server and everything has been great.
However
> > we are now moving to MS SQL 2000 in line with upsizing of our operations
> > and I was wondering if anyone out there had any recommendation as to how
to
> > get Perl DBI connectivity to MS SQL 2000.
> >
> > I have already tried:
> >             DBI:MSSQL
> > DBI:Sybase + FreeTDS
> > DBI:ODBC + Merant's Sequallink
> > DBI:ODBC + Openlink
> >
> > And can get none of them to work - however Merant's Sequalink seems the
> > most promising as it says that it can verify the DSN okay, However
DBI:ODBC
> > won't use it - says driver manager cant connect and no default driver
> > specified.
> >
> > If we can't get it connected we may have to consider other RADIUS
servers,
> > like bundled MS one, but hopefully we can get Radiator talking to the MS
> > SQL before then.
> >
> > Any comments would be appreciated.
> >
> > Regards,
> >             Jamz.
> >
> >   _____
> >
> >
> > Jamz Boman
> > Internal Systems Developer
> >  <http://www.airnet.com.au/>
> > Ph: (08) 8168 8068
> > Ph: (08) 8211 9200
> > 149 Currie Street, Adelaide
> > South Australia 5000
> > Australia
> > "I have as yet to establish a telepathic link to your computer, please
> > wait..."
> >                                     -- Andrew Hill on Customer Support
> 
> ----------------------------------------
> Content-Type: text/html; name="Attachment: 1"
> Content-Transfer-Encoding: quoted-printable
> Content-Description:
> ----------------------------------------
> 
> --
> Radiator: the most portable, flexible and configurable RADIUS server
> anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
> -
> Nets: internetwork inventory and management - graphical, extensible,
> flexible with hardware, software, platform and database independence.
> ===
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.