I'd like to install MongoDB Community Edition on my computer, which has the 64-bit Windows 10 Home OS, but the system requirements say I need Windows Server 2008 to do it.
I don't think my computer has Windows Server 2008. Is there any way around this? For example, would it work for small-scale databases, or is it totally incompatible without Windows Server 2008?
If I absolutely can't use MongoDB, is there another non-relational database that would work with my system? (It would have to be free.)
I admit that the download site is a bit confusing.
But you can simply download the MSI and install it on your Windows 10 machine. A Windows Server version is not required for the community edition.
Disclaimer: I have it on a Pro (Windows 7 and 10, without Windows 2008 or any other server) edition, not on a Home edition, but I'm pretty sure that it will work in the local machine context)
Related
i installed SQL Developer on my MacBook
when i tried to run the sql code it says must create new connection
it required username/password
so how can i solve this
before i was using oracle database XE 12 on windows 10
but now i am using macOS and i see i cant use this software anymore (oracle database XE 12)
so i tried to install SQL Developer
Oracle SQL Developer is a tool that lets you connect to an (Oracle) database. But - you have to have the database as well (apparently, there's none on your Mac).
Express Edition database you previously used on Windows 10 was (probably) 11g (not 12; it doesn't exist), but it woks on Windows an Linux - not macOS.
Moreover, none of the modern Oracle databases can be installed on Mac; the last one was, I think, 10g (but - as it is out of support, you can't even download it any more).
Therefore, you could install a virtual machine on Mac, put Windows OS onto it, download and install 11gXE along with SQL Developer and use it.
But, why bother? Install VirtualBox and then download one of Pre-Built Developer VMs (for Oracle VM VirtualBox).
When I go to https://www.mongodb.com/download-center#community I don't see a version specific to windows7 64bit to install?which version should I install for windows6?
Ok this seems not clear. But you need to use the Windows Server 2008 R2 64-Bit Installer, with or without SSL support.
The others are a 32-Bit version and a legay 64-Bit version of mongodb, that does not make use of some windows features.
So this (with SSL) or this (without SSL).
Heres a reference to the Installation instructions of MongoDB.
MongoDB for Windows 64-bit runs only on Windows Server 2008 R2, Windows 7 64-bit, and newer versions of Windows. This build takes advantage of recent enhancements to the Windows Platform and cannot operate on older versions of Windows.
MongoDB for Windows 64-bit Legacy runs on Windows Vista, and Windows Server 2008 and does not include recent performance enhancements.
I'm trying to set up a MEAN stack and I'm having the following issue when trying to execute mongo.exe: "The procedure entry point K32GetProcessMemoryInfo could not be located in the dynamic link library KERNEL32.dll"
I'm using Windows Vista 64bit, mongo is the latest, and I'm logged as administrator.
Thanks.
For Vista you need to install the Legacy version of MongoDb.
The 64-bit legacy build lacks newer features of Windows that enhance performance. Use this build for Windows Server 2003, 2008, or Windows Vista.
Here´s the Download link
Our product uses the JBoss 4.0.4 as an application server. Currently we are supporting Windows Server 2003 and planning to support Windows Server 2008. We want to know that is JBoss 4.0.4 fully compatible with Windows Server 2008 (64 bit)?
Please respond if anybody installed and used JBoss with Windows 2008.
Thanks
Since JBoss is 100% pure Java you can have it working on any Operating System that supports Java. So I guess that the real question is more "does my JVM run correctly on Windows 2008". According to this guide, JBoss needs a JDK 1.5 and should run on a 32-bit or 64-bit JVM on a 64-bit Windows 2008 machine.
I have basically succumbed to the fact that if you are a hardcore computer user, you will have to reimage your computer every few months because something bad happened. Because of this, I bought imaging software and then really got into imaging. I am now ready to move my development environment completely into a virtual machine so that I can test sites on IIS as though I am on a dev network (and backup these images easily).
The question is, what is the best virtual development platform for a 4 gb laptop? A virtual Vista Business with 3 gb of ram, windows XP sp3 with 3 gb of ram, or Windows Server 2003 with 3 gb of usable ram.
Tools I will need to install:
*sql server 2005 dev edition
*vs 2008 sp1
*tools for silverlight
*and multiple other smaller testing tools
I have tried the following combinations:
Windows XP SP3 on Virtual Server
2005 R2
Windows Vista Business
x64 on Virtual Server 2005 R2
Windows XP on Virtual PC 2007
Windows 2003 on Virtual Server 2005
R2
Windows XP on VMWare Fusion
and the Virtual Server installations where either local or hosted on a server and they all ran fine and about the same speed.
The VMWare Fusion Virtual Machine running under OS X is (seat of the pants) significantly faster than the others. I haven't tested VMWare on Windows to see if it is VMWare or the Hardware making the difference, but it's something worth looking into.
Server 2008, converted to a workstation.
Nothing compares IMO, I've loaded 3 Different OS's in the last 3 months, and I'm set on Server 2008.
I think the biggest question (from my standpoint) is whether or not you'll be doing development (like SharePoint) that requires a server platform. If you anticipate a lot of SharePoint development (or perhaps Exchange, or BizTalk, or another product that requires development be done on a server platform), then go with Windows Server 2003. If not, then I'd probably choose XP, though Vista isn't a bad development platform.
I personally prefer developing on a server platform - however, that opinion might shift if I was developing any sort of WinForms applications, since it would more correctly represent the OS family for the target audience.
I did notice a slight performance decrease going from Server 2003 to Server 2008 that I was not expecting, but that might be more from doing an in-place upgrade instead of starting clean.
From the options you gave, I would personally go with W2k3. You can really trim a server OS down to run lightning-fast, especially when you don't have or get rid of the MS "eye candy".