Windows 7 Pro 32 bit - Low on Memory... Ideas?
-
@donaldlandru said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
Section iii Device connections
In the case of a database application I would call this "synchronizing data" in which case there is no limitation.In no way whatsoever is this what that is, however. You can't just call database data synchronization. It's not at all. Not even kinda.
-
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@donaldlandru said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
Section iii Device connections
In the case of a database application I would call this "synchronizing data" in which case there is no limitation.In no way whatsoever is this what that is, however. You can't just call database data synchronization. It's not at all. Not even kinda.
I would say that depends on implementation.In the Oracle case, the transaction is wrote to the local database and then sent up to the lead database later.. Not sure how you wouldn't call that synchronization.
-
@donaldlandru said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
So tricky Microsoft at best.. Using this as my source:
MS is really never tricky. It seems that way because people always try to work around the licensing and to do so say it is tricky and act like they don't know what it is saying and aren't responsible for it. MS licensing is actually very straightforward and sensible in nearly all cases. MS licensing is so easy, in fact, that "logical licensing" is all that is needed - everything is licensed how it makes sense to be licensed. Nothing is weird or tricky or surprising. It's all just about exactly as we would expect it to be based on their product offerings and user base, with a few specifics (like 20 connections instead of 10) being the only real details to know.
Of course, just "assuming logical" isn't enough, you do have to verify it. But MS licensing is so easy that "if it doesn't seem simple and obvious", then almost certainly you have it wrong. MS licensing makes total sense in real world usage.
-
@donaldlandru said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
In the Oracle case, the transaction is wrote to the local database and then sent up to the lead database later.. Not sure how you wouldn't call that synchronization
By that logic, you can call literally all networking a "synchronization." Obviously that's not the case. That's not what anyone has ever thought that that meant before.
There is super basic, well understood data synchronization services like Robocopy, OneDrive, etc. Those are allowed. It's a type of file server that falls under the file server heading of that iii point that the synchronization was in.
-
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@donaldlandru said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
In the Oracle case, the transaction is wrote to the local database and then sent up to the lead database later.. Not sure how you wouldn't call that synchronization
By that logic, you can call literally all networking a "synchronization." Obviously that's not the case. That's not what anyone has ever thought that that meant before.
There is super basic, well understood data synchronization services like Robocopy, OneDrive, etc. Those are allowed. It's a type of file server that falls under the file server heading of that iii point that the synchronization was in.
I guess im confused - whats the difference between a filerserver and a database servers?
What makes them different?
I was told that these are "fileservers" not "database servers" - So wouldn't what we be doing be synchronization?
-
haha, just found this...
https://community.spiceworks.com/topic/1982878-windows-pro-os-as-an-application-server-cals-etc
"Correct, you must have CALs for any use of Windows Server like that. Yes, using Windows is expensive :)"
-
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
I guess im confused - whats the difference between a filerserver and a database servers?
A LOT. This is just IT basics. Hold on, I'll make a post.
-
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
I was told that these are "fileservers" not "database servers"
that's a flat out lie. So there's that. You KNOW that MS SQL Server is running and needed. So that it is a database server is completely known and there is no way to question that.
-
Hence my question of it it would work if you shut that down, to prove it had to be a database server, not only a file server.
Just because it is also a file server, doesn't give you a free database server. Otherwise, everyone would turn on file services and bypass the licensing.
-
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
I guess im confused - whats the difference between a filerserver and a database servers?
A LOT. This is just IT basics. Hold on, I'll make a post.
I just answered my own question : so correct me if I'm wrong here -
Since we are using My SQL Express we are using Database Servers .
If we weren't using SQL express ( like in old manager ) It would be a file server? -
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
Hence my question of it it would work if you shut that down, to prove it had to be a database server, not only a file server.
Just because it is also a file server, doesn't give you a free database server. Otherwise, everyone would turn on file services and bypass the licensing.
I literally just asked this quesiton
Why so fast? -
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
I guess im confused - whats the difference between a filerserver and a database servers?
What makes them different?https://mangolassi.it/topic/19222/database-server-vs-file-server-what-s-different
For easy comparison... just try using one of each. Use Microsoft's file server (literally its name is "server"). You use it by mapping a drive from another machine. Then try using SQL Server which you use by writing an application that talks to it over an API.
-
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
Since we are using My SQL Express we are using Database Servers .
If we weren't using SQL express ( like in old manager ) It would be a file server?The first part is easy to answer. You are using an MS SQL Server instance, so you are using a database server. Yes.
The second part is harder. We don't know what all is going on other than that one thing. It's easy to spot a clear violation. But knowing that "nothing else is wrong" is very hard, as we have no visibility into the system. BUT, if the old system communicated purely by mapped drives and used no services to communicate, then you'd be good as very limited file serving is allowed. But that's such a terrible system, that you'd "pay" in other ways.
-
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
Since we are using My SQL Express we are using Database Servers .
If we weren't using SQL express ( like in old manager ) It would be a file server?The first part is easy to answer. You are using an MS SQL Server instance, so you are using a database server. Yes.
The second part is harder. We don't know what all is going on other than that one thing. It's easy to spot a clear violation. But knowing that "nothing else is wrong" is very hard, as we have no visibility into the system. BUT, if the old system communicated purely by mapped drives and used no services to communicate, then you'd be good as very limited file serving is allowed. But that's such a terrible system, that you'd "pay" in other ways.
I think we still use mapped drives - How else would the data get pulled in by the front of house terminals?
SO correct me here - But If I use a database server instance to compile data into folders and then use a mapped drive to send data to and from on mapped drives then wouldn't I be a fileserver using a database instance - not making it a database server? -
Another thing that can be "indicative" is ports and services. If you are using absolutely nothing but a file server, you'd expect to see only one service running (called "server" on Windows), and no ports needing to be opened. If you are running something else, you'd expect there to be some other service running and whatever service that is would presumably need port(s) open for it to communicate.
What gets difficult is if something is using the file server as its communications channel to the outside world. This is where software can play some hiding games. This would be converting the file server protocols into an API. This gets very tricky. So there are totally ways to hide other services without running a service process or exposing ports. But it is messy and silly, but could be done to "hide" from a licensing audit.
-
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
I think we still use mapped drives - How else would the data get pulled in by the front of house terminals?
We know you use mapped drives. That's what I'm saying that having a file server as well doesn't give you a free database server. It is the database server that violates your license, not the file server component.
-
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
Another thing that can be "indicative" is ports and services. If you are using absolutely nothing but a file server, you'd expect to see only one service running (called "server" on Windows), and no ports needing to be opened. If you are running something else, you'd expect there to be some other service running and whatever service that is would presumably need port(s) open for it to communicate.
We use a "Ctlsvr" to run the front of house along with 'server' - would that be like what you're talking about?
-
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
I think we still use mapped drives - How else would the data get pulled in by the front of house terminals?
We know you use mapped drives. That's what I'm saying that having a file server as well doesn't give you a free database server. It is the database server that violates your license, not the file server component.
Oh!
Okay now it's starting to make sense -
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
SO correct me here - But If I use a database server instance to compile data into folders and then use a mapped drive to send data to and from on mapped drives then wouldn't I be a fileserver using a database instance - not making it a database server?
Then you are in even worse shape because this is so ridiculous a court would see it as "intent to defraud" by making a slow, terrible system that makes no sense except to attempt to hide that you are violating a license.
This would be still having a database server (can you get data from the database? Then you have a server), but coopting the file server protocols to do it turning them into an API and thereby requiring that they be licensed as a server to keep using.
No matter how you skin the cat here, it's still a cat. There is a database server, it is managing data, and it is getting that data to other machines. That another service is put into that process to hide that is bad programming practice, but doesn't change licensing. Licensing is by use and intent, not visible protocol.
-
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
We use a "Ctlsvr" to run the front of house along with 'server' - would that be like what you're talking about?
It might be. I don't have enough details on that particular service to know if it is or isn't. I know that that is a service of Aloha. But what I don't know is if that provides services to other machines or not. It might be a service that only does things for the machine on which it runs. We'd have to research that particular process more to know if it is only a local server (allowed on Windows 7/10) or a network server (not allowed on Windows 7/10.)
