Well its the first time i’m using MS server 2012 as a OS, ive taken the forum advice and trying to setup a proper server using server 2012 as an OS and I my setup is standalone with GUI, my problem is with connection to SAMBAPOS. The MSMS can connect correctly with Windows Authentication and with SQL authentication login using: username=sa & password=sambapos#1.
But when I use the same credential to log into the connection string for sambappos I cant seem to get a connection.
This version of Sambapos in hosted on the server so local host is accurate.
This is shown in your SSMS screenshot in the first line of the Object Explorer. It should also be shown on the Connection dialog when you first start SSMS, where you click “connect”.
When SambaPOS successfully connects, it should create a Database for you, as specified by the Connection String.
Or if you have a DB backup, you can use SSMS to restore the DB first, then launch SambaPOS:
right-click on the Databases node in the Object Explorer, and select Restore Database …
choose Device, and browse to the location of the Backup (it should be a .bak file)
optionally change the name of the DB that will be restored/created
For ease of setup in Multi-Terminal systems, we generally recommend using the “sa” account for all Terminals, but you may define other users for different Terminals or other purposes if you so choose.
You can backup and restore individual Databases using SSMS. When you use SSMS to restore a DB Backup, you also have the choice to rename the database, over-write (nearly) any DB within the Instance, or simply restore the backup using the original name contained in the Backup.
What would be really useful @QMcKay is a Startup parameters such as “-connectstr” that automatically brings up the connection string dialogue box before attempting to attach the DB.
As you have described if the string has an error SambaPOS just hangs and you need to find the hidden file SambaSettings,txt and manually edit it which I think is not such a great idea. Using a Start parameter also will help switching DB’s for Testing and Development purposes.
There is also this dialog that can appear, which forces a restart, but you edit the string in-place, click Ok, and the next time you start, it will attempt connection with the modified information …
The backup set holds a backup of a database other than the existing ‘SambaPOS4’ database.
The error you are getting during restore of DB with SSMS can be overcome if you look at the Options portion of the Restore dialog, and check these boxes (the first box is the important one for that error message, but it doesn’t hurt to check the other one as well):
You also have the option to relocate the physical DB files (MDF and LDF files) during a SSMS restore using the Files portion of the Restore dialog. This has nothing to do with the error, and is rarely necessary…