OK I am getting somewhere There's actually a couple of other changes - One in the source code - one for the queries. I have it running in theory and will test and come back on this one soon.... With the source code - the issue I found was the Transaction code was different in Mssql to mysql - The start / end transaction calls seem to be hard coded - so for now I have tweaked the code to send the MS SQL commit functions - BUT I suspect that may be better as a config setting ? I am going to test this 'in anger' now so we get accounting data for a few test accounts and make sure things look OK... Once working would you like a copy of the code changes / working queries to apply to the code ? Thanks for the help so far ... Richard On Saturday 06/04/2019 at 7:28 pm, Arran Cudbard-Bell wrote:
On Apr 6, 2019, at 8:18 AM, Richard J Palmer <richard@merula.net> wrote:
HI
I am looking at using this for some connections where a static IP address is not needed.
Currently we use mssql for the SQL server for the main radius process.
Looking at rlm_sqlippool there are queries for
mysql oracle postgresql sqlite
Before I start here - would this module support mssql if I create / tweak the queries - OR should I run a separate SQL server just for the IP Pools
I was not 100% sure after reading the documentation. More than happy to adjust the SQL (Create a table / create the queries) Just wanted to consult here before doing that.
Assuming it will work OK and I create a working config I am more than happy to provide it back to the project
Yes it'll work, you just need to create the queries.
-Arran
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Apr 6, 2019, at 3:54 PM, Richard J Palmer <richard@merula.net> wrote:
I am getting somewhere
Sounds good.
There's actually a couple of other changes - One in the source code - one for the queries.
I have it running in theory and will test and come back on this one soon....
With the source code - the issue I found was the Transaction code was different in Mssql to mysql - The start / end transaction calls seem to be hard coded - so for now I have tweaked the code to send the MS SQL commit functions - BUT I suspect that may be better as a config setting ?
The transaction code should be pretty common: start transaction, do work, end transaction. And all of those SQL statements can go into the configuration files. e.g. having "allocate_commit = COMMIT" in the source is just a default. If you need a different statement for commit, just put "allocate_commit = whatever" into the configuration files. No source code changes required. What's different about the MS-SQL commit functions?
I am going to test this 'in anger' now so we get accounting data for a few test accounts and make sure things look OK...
Once working would you like a copy of the code changes / working queries to apply to the code ?
Yes. Probably only one file with the queries is needed. Alan DeKok.
participants (2)
-
Alan DeKok -
Richard J Palmer