I have been using BarTender 9.4, 10.1, 2016 R6 (Automation) by [Seagull Scientific] for about a decade and I always installed my SQL Database on a SQL Server (Virtualized) while keeping BarTender on some other Virtual Machine. It just makes it easier to maintain and access. However if you upgrade to 2021 you CAN’T do that anymore, your database must be on the same server your BarTender is installed on (in other words install SQL or Install your BT on the SQL Server, thats poor practice). They consider having your database on another server an “Enterprise” feature, they always apparently have, I was told it was an oops-bug, in a few builds. Just a Heads-Up! Let me tell you Enterprise costs an arm and a leg, for just wanting to send CSVs to Commander/Integrations.
Remote SQL doesn’t mean SQL Server on Azure or Internet. It literally means a SQL Database on another Virtual Machine.
I can’t imagine how many users are applying best segregation practices, who will be surprised by this in 2021.
To Seagull, please consider allowing installing SQL on another server, as long as someone only has a single “Integrations” running. I can see you requiring an Enterprise license for those who need to have multiple Integrations instances running to load-balance workload, but if its a single, who cares where the database is as long as its 1.
They always stated that Remote SQL Server required Enterprise (however it wasnt defined what Remote meant), since it worked for many years, most people took that as “Remote SQL” means a SQL Server outside of my Domain - the Cloud, Azure, Internet. I never thought it was a SQL merely sitting in another Virtual Machine, since it always just worked fine. blah
How many of you who use BarTender have their Database on another Server?
@hkeric.wci - Thanks for the heads up. I am not using BT (yet) but I completely agree - NOTHING goes on my SQL Server except SQL. It’s the #1 rule, along with there’s only 2 people who know the SA password.
At some point my license was upgraded from “Enterprise Automation” to “Enterprise”… I purchased through Epicor. I think it must have happened when they retired the “Automation” edition.
Haso, is there a centralized administration console or does each client have its own admin console that you have to modify?
I am just now learning about bartender and as I was reading I thought, man I want a centralized system database, but then went to do that and realized I needed a different license- the enterprise license.
I moved on and thought, oh well. Then I started learning about the administration console. I thought, why is this on every client? Can I make it so that the client one is ignored and it uses centralized admin settings?
Is that a possibility in any license type (automation, enterprise, etc.)? Is this even an option to begin with?
Also, is there any way to remotely deploy this application and remove the installs for things like librarian, printer maestro, etc…? In other words, can you tell it to only install print station or bartender? @hasokeric
Haso, I assume you put SQL on your BT server instead of the reverse? Did you go with SQL Express on the BT machine or stand up an instance of SQL Server Standard (or Enterprise)?
We always only had 1 SQL Server, Enterprise. We didnt mix, and we kept SQL on its own Instance with all the Enterprise bells-and-whistles like Replication, Readonly, AlwaysOn, 1TB of RAM…
But I think in BT case due to this limitation, we just did SQL Express, its just for BT Logging.
