SQL Server 2012 Standard on Samba POS V5 - client connection issues

Hello everyone, I have a little problem with V5 database connection.

I installed everything exactly as in http://www.sambapos.org/en/content/installing-sql-express-2012-sambapos-v3

On the server, I can connect to the database just right using:
Data Source=localhost; Database=SampleSambaV5; User ID=sa; Password=123456ABC;

On the client in the same network, I’m using:
Data Source=; Database=SampleSambaV5; User ID=sa; Password=123456ABC;

But connection failed on the V5 client.

Now, I’m trying to use V4 client to connect to the database to make sure everything correct:
Data Source=; Database=SampleSambaV5; User ID=sa; Password=123456ABC;

V4 Client connect successfully but tell me I need a version check.

I wonder if you know about this issue and pass it somehow?

Check that you have opened appropriate ports on your servers firewall for sql server, and enabled tcp as the client connection protocol.

Specifically tcp port 1433

Dear nakchak,

As I mention above, V4 client connect successfully which means I have no problem with port forwarding… I’m really stuck here.

Show the connection error?

It’s so strange now kendash, this morning, when I’m trying to take a screensnap for you. V4 runs as expected. But, also the V5. I don’t know what is going on here. I’ll get back with more detail if I can find it out. I’m so sorry for he trouble.

BTW why 2012? 2014 is newest version and in fact even newer version due out soon.

I know you have it running already but here is the new tutorial for setting up SambaPOS SQL Express.

It was likely a network issue. There is no difference between how v5 connects to the database vs how v4 connects. So likely it was a network issue.

Is there any big difference between 2012 vs 2014’s performance? I will probably change to 2014 if things get faster and more stable.

I cant say if there is a difference but I have ran 2014 for quite a long while now and it runs just fine. Its best to stay with current software for security updates and life cycle support. SambaPOS is a very small footprint as far as database is concerned so likely you wont feel a difference in speed.

Here is an article that might explain some benefits:

1 Like

The topic is; “SQL Server 2012 Standard on Samba POS V5 - client connection issues”

SQL Server (xxxx) Standard is a different product compared to SQL Express (xxxx)
Some main differences:

  • SQL Server (xxxx) = not free, you will need a paid license
  • SQL Server (xxxx) allows more connections (sorry i’m to lazy to search the exact numbers)
  • SQL Server (xxxx) has windows integrated backup

But that said; I say for SambaPOS V5 go for SQL Express (xxxx) not SQL server

  • For SQL Express you don’t need a paid license
  • You can install the latest version so in a couple of years so you still get (security) updates even if your still running an old version of SambaPOS
  • I can’t imagine that anybody will hit the connection limits of SQL Express with any realistic amount of payment terminals in SambaPOS.
  • SambaPOS V5 has a backup of it’s own, you don’t need SQL Server or any script to do your Backup.
  • And did i mention that SQL Express is free? :wink:

Just my opinion: For really big Databases you should use SQL Server (If you really need Windows), but if you would like to improve SambaPOS preformance don’t invest money in SQL Server invest in a proper Solid State Disk (But that goes for about any PC still running on classic harddrives) and just go for SQL Express.

Ps. I have unused SQL Server licences myself, and i still go for SQL Express

Can’t see anything on vs Google about number of connections.
Differences I can see are how much ram and cores can be used with reviews pointing to the biggest difference being the max database size BUT with SQL express offering 10GB max size… Well if you can fill 10GB of database with samba alone I’ll buy you a server licence :-p
I won’t really but would be shocked if you can hit 10GB and would like to know how that is even posible… Maybe after 100 years of transactions LOL

You’re right, i’m mixing up some products it was the Database size what was the main limitaion.
I shouldn’t have been lazy then my reply would have made sense :stuck_out_tongue: