Windows 7 Pro 32 bit - Low on Memory... Ideas?
-
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@donaldlandru said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
With that said, Oracle Xstore is not even supported on Windows Server.
What this means is that the product simply isn't supported anywhere in the first world. It has no supported stack. For something to be "supported" in IT terms requires support end to end. With Xstore, this means that they don't have any support stack.
Lots of really crappy hobby class vendors (Oracle is this for sure) do this as a trick to guarantee zero legal accountability for support. If you run a desktop OS, they can claim that that isn't a server product and they can't support you (and they can threaten to turn you over to MS if they want - they have bilateral agreements for this through the BSA.) And if you don't run on a desktop OS, they can claim you don't fall under their support. This guarantees them an "out" to not support you no matter what you do. There is no possible end to end support path, none. It's impossible.
In IT terms, it simply means that it is an unsupported product. Across the board. It simply exists without support. Caveat emptor. Anyone buying it simply can't tell their companies that they got a supported product. They paid for commercial, closed source software without a support agreement. Oracle may or may not provide support, but is never required to. It's purely at their discretion.
Scott I just found this article.
https://logicalread.com/sql-server-express-as-a-production-database/#.XKZF-VVKjRY
Does this hold an real validation?
So I saw nothing amiss in the article. But I also found nothing related to this discussion in it, either. The article is about MS SQL Server, which was never in question. It is Windows 7 that is being used instead of paying for the Windows Server license which is required. That MS SQL Server is involved is neither here nor there.
we use MS SQL Server Express.
I guess I just thought it was related. -
MS SQL Server Express is absolutely, without question, allowed to be used in production.
To use it as a production server providing services to others, it must be run on an OS that is allowed to run it in that way. This would be either a Windows Server OS, or any Linux OS for free. So there is a free option for this (even cheaper than a Windows desktop.)
To use it as a development station without providing services to others, it can be run absolutely anywhere including a Windows desktop OS.
-
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
we use MS SQL Server Express.
I guess I just thought it was related.We know you do. But no one is questioning anything about that.
Imagine that we were having a restaurant discussion and the police stop you for stealing a hamburger. And you point out that you bought french fries. Yes, you bought french fries, but that really doesn't change the fact that you ran away with a stolen hamburger.
-
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@donaldlandru said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
With that said, Oracle Xstore is not even supported on Windows Server.
What this means is that the product simply isn't supported anywhere in the first world. It has no supported stack. For something to be "supported" in IT terms requires support end to end. With Xstore, this means that they don't have any support stack.
Lots of really crappy hobby class vendors (Oracle is this for sure) do this as a trick to guarantee zero legal accountability for support. If you run a desktop OS, they can claim that that isn't a server product and they can't support you (and they can threaten to turn you over to MS if they want - they have bilateral agreements for this through the BSA.) And if you don't run on a desktop OS, they can claim you don't fall under their support. This guarantees them an "out" to not support you no matter what you do. There is no possible end to end support path, none. It's impossible.
In IT terms, it simply means that it is an unsupported product. Across the board. It simply exists without support. Caveat emptor. Anyone buying it simply can't tell their companies that they got a supported product. They paid for commercial, closed source software without a support agreement. Oracle may or may not provide support, but is never required to. It's purely at their discretion.
Scott I just found this article.
https://logicalread.com/sql-server-express-as-a-production-database/#.XKZF-VVKjRY
Does this hold an real validation?
So I saw nothing amiss in the article. But I also found nothing related to this discussion in it, either. The article is about MS SQL Server, which was never in question. It is Windows 7 that is being used instead of paying for the Windows Server license which is required. That MS SQL Server is involved is neither here nor there.
I think he is referring to the last section which doesn't relate to licensing just where the software will run
SQL Server Express is a great choice for small-scale, cost-effective multi-user database implementations. It can run on both Windows
desktop operating systems like Windows 7, 8, 8.1, and 10, as well as server operating systems like Windows Server 2008, 2008 R2, 2012, and 2012 R2. It is completely compatible with the Standard, Business Intelligence, and Enterprise editions of SQL Server 2014, and can be upgraded to any of these editions. Microsoft SQL Server Express is employed by many Independent Software Vendors (ISVs) as a built-in database and it can be included in your own installation packages. You can download all of the SQL Server 2014 Express editions for free from Download Microsoft SQL Server 2014 Express. -
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
we use MS SQL Server Express.
I guess I just thought it was related.We know you do. But no one is questioning anything about that.
Imagine that we were having a restaurant discussion and the police stop you for stealing a hamburger. And you point out that you bought french fries. Yes, you bought french fries, but that really doesn't change the fact that you ran away with a stolen hamburger.
Ah, Fair enough. Thanks for clearing that up
-
@donaldlandru said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
which doesn't relate to licensing just where the software will run
Correct. It can run there, and there are use cases where that is legal, but it never says that it can run there and be used as a server.
And MS SQL Server licensing, like Oracle or Aloha licensing, isn't related to the OS licensing. Even thought MS SQL Server is currently made by Microsoft, as is the OS, this was not always the case and isn't really relevant. Stating where something "can" run, is unrelated to "specific situations where different kinds of licensing are required."
-
Think about it more like this...
You have a primary product: Windows Server. You have to pay for this to use this (using Windows 7 in this way is using Windows Server without paying for it.) The agreement, or licensing situation, involved here is between you and Microsoft for this one product. That's one discussion.
Then you have a secondary product vendor. This could be anyone. Oracle, NCR Aloha, MS SQL Server Express, etc. By buying a product from this third party, it doesn't give you free access to Windows Server. That would make no sense.
Video coming because I like the analogy and want to do it justice.
-
@scottalanmiller said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
Think about it more like this...
You have a primary product: Windows Server. You have to pay for this to use this (using Windows 7 in this way is using Windows Server without paying for it.) The agreement, or licensing situation, involved here is between you and Microsoft for this one product. That's one discussion.
Then you have a secondary product vendor. This could be anyone. Oracle, NCR Aloha, MS SQL Server Express, etc. By buying a product from this third party, it doesn't give you free access to Windows Server. That would make no sense.
ok that makes sense.
Video coming because I like the analogy and want to do it justice.
Sounds good, You're going to use my information here?
Id much rather you keep it generic and reference to me or Aloha be excluded. if possible. -
-
So tricky Microsoft at best.. Using this as my source:
https://www.microsoft.com/en-us/Useterms/Retail/Windows/10/UseTerms_Retail_Windows_10_English.htm
Restrictions. The device manufacturer or installer and Microsoft reserve all rights (such as rights under intellectual property laws) not expressly granted in this agreement. For example, this license does not give you any right to, and you may not:
(i) use or virtualize features of the software separately;
(ii) publish, copy (other than the permitted backup copy), rent, lease, or lend the software;
(iii) transfer the software (except as permitted by this agreement);
(iv) work around any technical restrictions or limitations in the software;
(v) use the software as server software, for commercial hosting, make the software available for simultaneous use by multiple users over a network, install the software on a server and allow users to access it remotely, or install the software on a device for use only by remote users;
(vi) reverse engineer, decompile, or disassemble the software, or attempt to do so, except and only to the extent that the foregoing restriction is (a) permitted by applicable law; (b) permitted by licensing terms governing the use of open-source components that may be included with the software; or (c) required to debug changes to any libraries licensed under the GNU Lesser General Public License which are included with and linked to by the software; and
(vii) when using Internet-based features you may not use those features in any way that could interfere with anyone else’s use of them, or to try to gain access to or use any service, data, account, or network, in an unauthorized manner.
Section v
So, I interpret this as using the OS over the network (i.e. Remote desktop connetions)Multi use scenarios.
(i) Multiple versions. If when acquiring the software you were provided with multiple versions (such as 32-bit and 64-bit versions), you may install and activate only one of those versions at a time.
(ii) Multiple or pooled connections. Hardware or software you use to multiplex or pool connections, or reduce the number of devices or users that access or use the software, does not reduce the number of licenses you need. You may only use such hardware or software if you have a license for each instance of the software you are using.
(iii) Device connections. You may allow up to 20 other devices to access the software installed on the licensed device for the purpose of using the following software features: file services, print services, Internet information services, and Internet connection sharing and telephony services on the licensed device. You may allow any number of devices to access the software on the licensed device to synchronize data between devices. This section does not mean, however, that you have the right to install the software, or use the primary function of the software (other than the features listed in this section), on any of these other devices.
(iv) Use in a virtualized environment. This license allows you to install only one instance of the software for use on one device, whether that device is physical or virtual. If you want to use the software on more than one virtual device, you must obtain a separate license for each instance.
(v) Remote access. No more than once every 90 days, you may designate a single user who physically uses the licensed device as the licensed user. The licensed user may access the licensed device from another device using remote access technologies. Other users, at different times, may access the licensed device from another device using remote access technologies, but only on devices separately licensed to run the same or higher edition of this software.
(vi) Remote assistance. You may use remote assistance technologies to share an active session without obtaining any additional licenses for the software. Remote assistance allows one user to connect directly to another user’s computer, usually to correct problems.
Section iii Device connections
In the case of a database application I would call this "synchronizing data" in which case there is no limitation. -
Section iii Device connections
In the case of a database application I would call this "synchronizing data" in which case there is no limitation.That's basically all it's doing is syncing the data to the front of house.
-
@scottalanmiller I dont have speakers or head phone so i was like speed reading and was so confused when you got up I dont know what happened
But I like the anology. -
@WrCombs said in Windows 7 Pro 32 bit - Low on Memory... Ideas?:
Sounds good, You're going to use my information here?
Full name, SS#, Photo, etc.
-
@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.
