RadiusNT 2.5.267 Accounting stopped working with sp_dbcmptlevel set to 70.
Then RadiusNT crashed.
I switched sp_dbcmptlevel back to 65 and everything returned to normal.
> -----Original Message-----
> From: email@example.com
> [mailto:firstname.lastname@example.org]On Behalf Of Dale E. Reed Jr.
> Sent: Wednesday, January 19, 2000 3:55 PM
> To: email@example.com
> Subject: Re: [Emerald] Emerald and sp_dbcmptlevel
> Bernard Andrys wrote:
> > I ran a query and found my SQL 7 is set to SQL 6.5
> compatibility. (Which I
> > didn't do so I'm not sure how it got set.) Are there any problems using
> > Emerald client 2.5.294 with sp_dbcmptlevel set to 70?
> No. Thats actually the default.
> > (I've seen scripts posted by Dale before saying "you need to be running
> > 7.0", but I want to be sure that none of the stored procedures
> that Emerald
> > 2.5.294 call NEED to be SQL 6.5)
> Nope. SQL 7 has new functions/features that some scripts use (like
> replace) that 6.5 doesn't have. Those are the ones that need 7.0.
> Its not a sp_dbcmptlevel issue.
> > The reason for this is I want to run: ALTER TABLE Calls ALTER COLUMN
> > UserName VARCHAR(32) NULL
> > to change the length of the UserName column to match the length of the
> > UserName column in the Subaccounts table.
> Thats fine. I would just use Enterprise manager to change the designe
> of the table. Its much better than SQL scripts.
> Dale E. Reed Jr. Emerald and RadiusNT
> IEA Software, Inc. www.iea-software.com
> For more information about this list (including removal) go to:
For more information about this list (including removal) go to: