I have a sql server instance on a machine that I want to open up to being accessible over the network. However, I think there's multiple issues at play here and I'm not sure which one is the real contributing factor.
The version I'm using is:
select ##version
Microsoft SQL Server 2014 - 12.0.2269.0 (X64) Jun 10 2015 03:35:45 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 (Build 14393: )
I believe I need to enable network configuration in the SQL Server Configuration Manager, but when I look into my manager, I don't see anything of use:
Is there anything that clearly leaps out as to why this would be blank? Am I going about this the right way?
Re-install SQL Server and/or OS as necessary.
See similar questions here and here. What version is your OS? This is possibly an architecture mismatch - 64-bit SQL on 32-bit machine? Or version mismatch. SQL Enterprise installed on Windows Home edition?
Yes, you may be able to troubleshoot and fix, but SQL installs do some heavy lifting. The best and most thorough solution here is clean up and start fresh. It will provide you peace of mind.
Related
Am currently working through the mspress book to do the exam 70-462 and one of the questions asks what versions of sql and windows server reporting services can be installed on.
I was quite shocked to find that it said that Reporting services cannot be installed on a windows server 2008 R2 SP1 for SQL Enterprise edition.
I really dont see how this could be the case and having trawled through the msdn documentation cannot find any evidence to support this.
Can anyone shine any light on whether this is the case?
Thanks
You should be able to install it on Windows Server 2008 R2 according to the following paragraph found on the link below it:
"Starting in SQL Server 2008 R2, the Reporting Services component no longer supports Itanium-based servers running Windows Server 2003 or Windows Server 2003 R2. Reporting Services continues to support other 64-bit operating systems, including Windows Server°2008 for Itanium-Based Systems and Windows Server°2008°R2 for Itanium-Based Systems. To upgrade to SQL Server 2008 R2 from a SQL Server 2008 installation with Reporting Services on an Itanium-based system edition of Windows Server 2003 or Windows Server 2003 R2, you must first upgrade the operating system."
http://technet.microsoft.com/en-us/library/ms143506(v=sql.105).aspx
It is under: Processor, Memory, and Operating System Requirements.
I'm looking to test some of the new features in Hyper-V 2012 (v3).
Hyper-V v3 can be downloaded as a "free" version "Hyper-V Server 2012", or it can be purchased as part of Windows Server 2012 Standard or datacenter. However, as usual licensing is unclear.
On the one hand MS talk about their free edition in several (many) sites. On the other hand, when you go to the actual download site it talks about a trial. To me a trial has an expiry date so it makes me nervous.
I could use my Windows Standard 2012 license as part of my Microsoft Action Pack Subscription (MAPS), but I'm not sure what I'm actually entitled to.
So my question is:
What are the real differences between the free (trial) download of Hyper-V Server 2012 and the paid-for Windows Server Core 2012 where you have to install with a key.
Does the "trial" version actually expire?
No, Hyper-V Server 2012 doesn't expire.
Hyper-V Server is quite a bit like Server Standard Core with all of the roles except Hyper-V (and other supporting roles and features) removed.
Now, in Server 2012, you can add the full UI back to the Server Core editions, but that's not an option with Hyper-V Server 2012 - it will always just be a command-line. That also means that the typical management UI tools won't run on Hyper-V Server 2012, so you'll need a machine that you can manage it from remotely (the PowerShell cmdlets for Hyper-V actually do work on Hyper-V Server, though).
Hyper-V Server isn't really for people who want to "play around" with Hyper-V - it's really designed for people who want to boost their Hyper-V infrastructure with more physical hosts, and who want to run a very lightweight OS in the root partition, leaving the most resources available for the VMs.
If you just want to get used to Hyper-V or test some things out with it, but you don't have experience with managing Hyper-V remotely already, stick with a full version of Windows Server (or Windows 8 Pro/Enterprise x64, which also have Hyper-V).
I have some basic experience using sql server 2008 R2 (server management studio). I was wondering if the express version can be installed and used on a non server computer (os = MS XP). I have a simple web app that I want to test/practice connecting to the db, and performing simple insert/delete/update commands on a table. Can this be done?
Thank you
Yes, SQL Server Express can be installed on any Windows operating system, including the "client" OSes, except Windows CE of course, but that's something else.
You can use SSMS against SQL Server Express too, although some features of SSMS will be disabled becuase the server doesn't support them.
Yes, it can be done.
Supported operating systems: Windows 7, Windows Server 2003, Windows
Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP
Check this:
Microsoft SQL Server 2008 R2 RTM - Express
Microsoft does offer SQL express, which probably offers more functionality than you would probably need right now.
http://www.microsoft.com/sqlserver/en/us/editions/2012-editions/express.aspx
Not only would you need MSSQL, you would need to have a current version of IIS installed. Is there a reason you are particularly interested in MSSQL? There are other "package" installations available of PHP/MYSQL which are more simple in setting up such as XAMPP:
http://www.apachefriends.org/en/xampp-beta.html
I would like to know if I migrate from Windows Server 2003 to Windows Server 2008 (x64) do I have to reinstall all applications in new Operating System or I will be able to simply upgrade the OS without any data loss.
Check out this MS Technet Forum thread.
Windows Server 2003 and Windows Server 2003 R2 can both be upgraded in-place to Windows Server 2008, as long as you keep the following in mind:
The Windows Server 2003 patchlevel should be at least Service Pack 1
You can't upgrade across architectures (x86, x64 & Itanium)
Standard Edition can be upgraded to both Standard and Enterprise Edition
Enterprise Edition can be upgraded to Enterprise Edition only
Datacenter Edition can be upgraded to Datacenter Edition only
This might be your preferred option when:
Your Active Directory Domain Controllers can still last three to five years economically and technically)
You worked hard to get your Active Directory in the shape it's in.
Your servers are in tip-top shape.
I'm in the process of looking for a dedicated server to host my soon to be released web apps. THey are build with ASP.NEt and uses Sql Server 2005. I've got a great deal with a company for a Intel Core2Quad Q9300 with 8Gb or ram and 750Gb sata.
They offer me Windows 2003 64 Standard or Windows 2008 64 Web for free, which one should I choose?
My main concern is about the database, in the first moment I'm going to have only one box to host both the web and database layer. Will I be able to install SQL Server (initially the express edition, then eventually the standard) on the Web version of Windows 2008?
If you can get Server 2008, i'd go with it because IIS7 is an excellent Upgrade to IIS6.
SQL Server Standard 2008 64-Bit is officially supported on Windows 2008 Web Server. SQL Server Enterprise 2008 64-Bit is NOT (not sure if it does work and is only not listed. 32-Bit Enterprise is listed, but running 32-Bit on a modern server does not sound appealing). See System Requirements here for a full list of SQL Server 2008 Editions and supported Servers.
Not sure about SQL Server 2005, there seems to be a patch needed.
You can run SQL Server on Server 2008 Web Edition (this is a change from Server 2003 Web Edition). The main limitations I am aware of between Web and Standard for 2008 is Web cannot do any kind of virtualization, Active Directory or DNS management, etc. It is intended to be essentially an application server.
I would recommend the newer OS, since it comes with IIS7 and the enhanced TCP/IP (among other things).
If its free, go for the standard version. Here is a comparison of the features:
http://www.microsoft.com/windowsserver2008/en/us/compare-features.aspx
I've never noticed any performance differences in the versions, so might as well get features you might use someday. Expensive to upgrade later.
You can run the SQL on either one.