[LukePBX]

Hi all, I'd like to use MS SQL Server (either the free ms sql server express ) as database because it's scalability and our know-out about it.

[welsh]

AWESOME! Glad to see someone else is thinking about this.

To me, this is especially important for a product designed for Windows.

Kevin

[yolandaceron]

I have to agree, using Microsoft SQL Server as a database server will make this product more appealing to the Windows system. I hope this will be implemented in the future.

[tpinnovations]

MSSQL would be nice, especially if calling logging was recorded there.

[savant]

I agree that this would be a nice feature to have.

[greenshield]

I would like to vote for this one too.

[KerryG]

Other than for customized reporting tools, why would it matter if it used SQL Server specifically? The current design isn't bottleknecking at the dbase reads/writes so I don't see how switching to SQL Server would affect scalability or acceptance.

[comresource]

Other than for customized reporting tools, why would it matter if it used SQL Server specifically? The current design isn't bottleknecking at the dbase reads/writes so I don't see how switching to SQL Server would affect scalability or acceptance.

While I am not a DB guy at all, I certainly see a benefit from a SQL based backend. After all the primary selling point of 3CX is that it is a Windows based system and should take full advantage of this. There are a ton of MS SQL based management tools available that would open up a lot of custom apps to be readily developed. You yourself mentioned it would be nice to have a remote Call Reporter. With a database with integrated windows security this would be pretty easy to implement with MS SQL.

[brianp]

Count me in on this vote.

[peterbunn]

I'm not to sure about putting MS SQL with it. I like that all you need to do is install 1 thing and you're away.. I think thats what is gonna sell it for a Technician.

[tpinnovations]

A good portion of business's have a SQL Server somewhere in their organization. But I think it is not going to be a matter of it requiring SQL server, but rather having the option of using it. I think the more database portability it has, the more chances there are for integration.

[peterbunn]

True, I like the option idea. Because recently one of my client's SQL server has gone down and those not being able to do much work/get sharepoint.

[KerryG]

Simple ODBC connectivity to the dbase would give you all that without caring what the underlying engine is

[bgrubbs]

I think the main appeal for 3CX is that it is one of the very few PBXs that run on Windows and that is intriguing to a lot of people. Some would argue that it doesn’t make a difference what OS the PBX runs on as long as it has the capabilities you need, but I disagree. I’ve been tinkering around with VOIP servers for a several years and I was relieved to find 3CX after using Asterisk for so long. The reason I was relieved was because it is so much easier for me to administer a Windows server because I am more familiar with it, not necessarily because the features are better than Asterisk.

I think the same comparison can be made with the database. The reason to switch to SQL Server isn’t necessarily because of any feature or performance, but because most IT shops running Windows servers are going to be more familiar with (and have the staff that can support) SQL Server and are going to feel more comfortable if they have the option of using this DB.

I think 3CX is missing a huge opportunity here, especially if they are marketing themselves as a “PBX for Windows”. Using SQL Server will make them much more viable to enterprise shops primarily using Microsoft servers. I requested 3CX switch to IIS and SQL Server 3 years ago (see here & here). They made the right decision with IIS, now they need to just do the same with SQL Server.

[computer25]

I totally agree of adding Ms SQL Support which could be as an option to use the built in DB or the SQL, just like when selecting the web server : Cassini or IIS.