I note that the full version of Windows 10 can be run on a RPI 3.
I wondered whether SQL Server Express (or any other edition) is available for the ARM version of Windows. I can’t see it anywhere so I suspect the answer is ‘no’ but want to check I have my missed a trick anywhere.
Effectively I am testing out working with a large SQL Server database. I don’t want my test code to touch the actual site, so my plan was to run a minimal example with some test records locally on my desk. I have an old Atom-based machine I can use - but the RPi is a much more convenient in terms of having a ‘portable’ demo server.
I am aware any such setup will perform awfully - performance not an issue for the demo.
There are two questions here :
Is there a SQL Server version that runs on ARM?
According to the Operating System requirements no. SQL Server is only available for Windows IoT Enterprise, essentially a Windows 10 Enterprise version with special licensing. It's the evolution of Windows Embedded and only meant for OEMs that produce 1000s of devices.
And the real question
I don’t want my test code to touch the actual site, so my plan was to run a minimal example
In that case you can use Windows 10 containers, a VM or a managed cloud version of SQL Server. SQL Server docker images are available for the Express and Developer edition.
No, in contrast with .net, powershell and other initiatives, up to this point there is no ARM version of SQL Server. And by knowing how existing version was ported, we hardly can expect that it will appear soon on this platform.
Related
I have been supporting a product written in VB6 with an Access database for a long time. In many of the installations a mapped drive was used to allow multiple workstations to run simultaneously. Since it seems Microsoft has broken that recently, I need to re-write everything with a new set of tools.
I plan to use VB.net and I would like to use a SQL database this time for the stability. The problem is that the market I sell to cannot / will not support installing full blown SQL Server and all the complexities of managing it.
What I am not able to find any current info about is whether or not SQL Server Compact still exists, whether or not it can be added to a NON web based project and if it will be easy to deploy and be easy to manage like an Access database was.
When I try to follow the directions to add SQL Server Compact to my project, it isn't available in the Data Source drop down list (there are "Simple by ErikEJ" versions listed but they don't seem to work) I have seen SQL Server Compact talked about with regards to web projects but I am building a locally installed .exe. I can't find ANY current info about what flavors of SQL are available right now to add to a local program running over a peer to peer network.
SQL Server Compact is no longer supported and developed by Microsoft, I suggest that you use SQL Server Express, it allows remote connections (if configured to allow it) and has modest resource requirements. Supports a database up to 10 GB of size.
As suggested, SQL Server CE can still be used but is no longer supported. For file-based databases, Microsoft currently recommend SQLite.
For a multi-user system, SQL Server Express is probably your best bet. It's still server-based though, so the server needs to be installed somewhere. For local databases, you can install on the same machine as the application and attach a data file on demand. For multiple clients, you'll need the server installed on a machine accessible to all and a permanently-attached database.
I have a project where the choice of database engine is still up in the air, based on affordability and feature-set. Some basic groundwork has been carried out using SQL Server, and in evaluating the cost implications of opting to adopt SQL Server, versus a different vendor's product, I noticed that Microsoft has just released their public preview of SQL Server v.Next, which allows one to run SQL Server on a Linux platform.
According to www.theregister.co.uk, the public preview is a SQL Server executable that runs on *nix-based systems by utilising Drawbridge, which is essentially a way of running Windows applications on a tiny version of the Windows 8 kernel, run inside a sandbox.
One issue most open source advocates have had with Microsoft's SQL Server is that SQL Server Enterprise contains all functionality, and when opting for a more budget-friendly version, certain limitations are imposed on you.
Specifically, Standard Edition and Web Edition impose upper limits on in-memory column store (32GB and 16GB respectively), and Web Edition removes backup compression as a feature.
I've searched the web in an attempt to find out how Microsoft intends to license SQL Server as far as Linux versions are concerned, my main concern being related to database mirroring. As far as database mirroring is concerned, SQL Server Standard and SQL Server Web Editions both have a subset of the functionality provided by SQL Server Enterprise.
I'm looking to understand three things:
How is Microsoft going to license SQL Server vNext for Linux (specifically, the Ubuntu version)?
If vNext is a subset of the functionality of the Windows version of SQL Server, what functionality is omitted?
Is database mirroring functionality present in the Linux distros of SQL Server vNext?
I don't think licensing information has been released yet.
What we do know is SQL Server Next on Windows & Linux will run a single feature set. Here is a quote taken from MS at Connect().
Microsoft officials said SQL Server Next on Linux and SQL Server Next
on Windows are based on a single code base. "There are some features
that have platform specific characteristics. For example, file paths
in Linux are different than file paths in Windows," said a
spokesperson. But they are not two completely different products.
My take on this is: SQL Server 2018 (or whatever it ends up being called) will be the same on Linux and Windows. This lines up with the big news about SQL Server 2016 Service Pack 1. MS have announced all editions will be functionally the same, from LocalDb to Enterprise.
While the Linux version remains in preview it is hard be sure what the final product will look like. If this is choice you have to make soon you may well feel the Linux solution isn't, quite, ready for prime-time.
I am installing SQL Server 2008 R2 Web on my Mac (OS X Leopard), running Parallels 6 and Windows 7...
The database will be used for ASP.NET development purposes. I am trying to figure out what Windows Accounts to use for each SQL 2008 Service when prompted by the installation (e.g. SQL Server Agent, SQL Server Database Engine, SQL Server Reporting Services, SQL Server Full-Text Filter Daemon Launcher and SQL Server Browser). If I can simply create a new user account and use it for each service, that is okay, I've seen an example of that here. I guess my concerns are twofold:
Making sure that the accounts I wind up using have the proper
privileges suitable for vs2010 development/debugging.
Making sure that the accounts I wind up using do not pose any security concerns
associated with my mac
Firstly, Windows 7 is not a supported OS for SQL Server Web Edition, so it's unlikely that what you're trying to do will even work. I don't know anything about Parallels, but if it is a similar concept to VMWare then I guess that your Windows 7 installation should behave like any other Windows 7 installation.
Second, the considerations for SQL Server service accounts are well documented, including security issues, and so is the setup required for debugging in Visual Studio.
Finally, and for what it's worth, developing software of any kind in an 'unusual' environment that isn't the same as the environment where the application will be deployed usually leads to problems. It's just much easier and more reliable to develop in a 'native' environment, although I appreciate that if you're doing this as a hobby then you may not be able to have exactly the resources you want. If you're doing this professionally, you should be able to justify the cost of a native development environment.
Our production Sharepoint server serves around 800 users and runs together with its SQL Server on a physical dual-core machine.
The network guys now to put as much as possible on VMWare. The Sharepoint server and the SQL Server will be put on different servers.
Does anyone have experience of running a production-level Sharepoint server on a VM?
The sharepoint server: yes. The database server: I wouldn't.
Our organisation is backing away from virtual database servers and going towards large multi-node, multi-instance clusters.
Most of our app/web servers are virtual.
We run SharePoint and SQL Server on separate VMs on VMWare ESX in our datacenter. ESX does not add much of a disk I/O performance hit, but the trick is to use fast drives (15K RPM). We found that SharePoint page load times were greatly improved by this simple change in the hardware. Since all of the configuration data for SharePoint is stored in SQL Server, all page loads are dependent on reading data out of the DB, and assembling it in IIS.
We run CRM under VMWare with no problems. If you have a properly configured ESX 3.0 or 3.5, with appropriate resources it is perfectly OK.
Have a look what Michael Noel says
http://blogs.technet.com/virtualization/
He has a ppt where he also speaks about things to look after
http://www.google.se/url?sa=t&source=web&ct=&cd=5&url=http%3A%2F%2Fwww.sharepointusers.org.au%2FSydney%2FUser%2520Group%2520Presentations%2FVirtualizingSPComponents%2520-%2520November%25202008.ppt&ei=4vTdScutFtbisAb6j92zDA&usg=AFQjCNF5D68IsDrtTqTlQj075BNJ9COi9A&sig2=pVr_iV_9Gvt9Icxx4iq7Eg
I have been in a project where we have had performance issues with Sharepoint and the feeling I have is that if you have a virtual environment this is what people mostly blame. Dependent if it is just a out of the box Sharepoint installation or a more customized mission critical environment I should at least think about doing some Load tests and see how the installation scales....
Regards
Magnus
Ps. lesson learned is that you have to test where the limits are...
Remember Microsoft's supportability before virtualizing any environment:
Microsoft server software and supported virtualization environments
http://support.microsoft.com/kb/957006/en-us
This link tells about which products are supported under virtualized environments
Windows Server Catalog
http://www.windowsservercatalog.com/results.aspx?&bCatID=1521&cpID=0&avc=0&ava=0&avq=0&OR=1&PGS=25
This link defines which hardware vitualization softwares Microsoft Supports
Sharepoint Portal Server 2003 isn't supported when vitualized, that means that if you have a problem and need Microsoft's help, you'll have to reproduce it in a physical box.
We are a small company and would like to know the best possible (and affordable) hardware and software configuration we ought to be using for our development environment. At this moment we are a team of four people who work remotely from different locations and each one of us uses a laptop and ADSL connection to work on our projects.
This question should help us identify a path towards optimizing our hardware and software so as to make the most of these development environments. Do we need to run everything locally on the laptops or some sort of distributed solution is possible? Which software versions do you recommend given that both Windows 2008 and SQL Server 2008 are available options? Do we use a central server or run these locally on our laptops?
We're a young team so any help would be welcome and much appreciated! Thanks!
Ym
For a team, I would suggest that you set up the local environments (laptops) as development environments, with a local DB copy and running CF developer version. Version control (VSS, Subversion, Git, etc.) is pretty much mandatory.
Have a testing/staging/QA server with the same configuration as the live version (as much as this is possible). It should have its own CF license to follow the licensing agreement. You should put checked-in code here for everyone to test and to check integration. Several version control systems offer ways to automate this, or you could do this manually.
Production, obviously, should be its own thing. I would suggest that you separate the database and app/web server on two separate boxes.
I know this might be a little more/less than you were asking, so feel free to ask for clarification.
For either ASP.NET or ColdFusion, You'll want to have the developers set up with their own local development environments on their Laptops. With ColdFusion, this probably means ColdFusion 8 Developer Edition (Free) and either MySQL (Free) or MS SQL Express Edition 2008 (also Free). For the actual development, you'll want Visual Studio 2008 ($170 -> $1400) for ASP.NET development, or Eclipse with CFEclipse plugin (Free) for ColdFusion Development.
You will almost certainly need a testing/QA string of servers, with ColdFusion 8 ($1300) you can run Linux, MacOS X, or Windows Server. ASP.NET pretty much requires Windows Server 2003, but if you're feeling adventurous, you could probably use Linux or MacOSX with Mono (Free) For your database engine, you can use MySQL (Free), PostgreSQL(Free), MS SQL ($6000), or one of many others.
Your production environment should be basically the same as your testing/QA environment, though depending on your traffic, you may end up with some esoteric load-balancing solutions. If you reach the point where this is necessary, you'll be able to afford to hire someone to answer this question for you :)
MS SQL Server 2008 Express, it's free.
http://www.microsoft.com/downloads/details.aspx?familyid=B5D1B8C3-FDA5-4508-B0D0-1311D670E336&displaylang=en
Windows XP (prof. edition) is stable and use less resources than Vista.
For asp.net I suggest using Dev Studio 2008 Pro.
For the computer itself, you want lots of memory (2-4 GB). A fast dual-core CPU. And you will see a difference using a faster HD (on a laptop, 5400 RPM HD are fast and 4500 RPM are the standard)
I recommend working locally and update all on a central location (with source control as Ben wrote).
I would use whatever server hardware you can afford 1/2/3 machines with plenty of ram and disk space and use Virtual server, or vmware server. That way you can simulate a ntier architecture. You can VPN/rdp/sslvpn etc to the virtual machines for your QA environment.
My QA environment has 7 machines, I have 3 physical servers, the biggest server runs SQL 2005 ent on the physical machine, it hosts 2 virtual machines one being the domain controller that all machines use for authentication. the 2 other server each host a virtual machine each.
That way i have a 3 tier architecture for QA and a separate 3 tier architecture for UAT.
Virtual machines are easy to spin up/ copy etc.