I was browsing my technet downloads for SQL Server 2012 and I noticed a bunch of products labelled "core" edition:
Is this something to do with their new per-core licensing model, or something else?
I'm installing the 180 day trial of SQL Server 2012 on a virtual machine with the intent of buying a license for it later on. From past experiences with installing SQL Server I would always make specific user accounts for the SQL Server to use. Looking at the installer now, its pre-populating the accounts with specific ones of its own:
- SQL Server Agent - NT Service\SQLSERVERAGENT
- SQL Server Database Engine - NT Service\MSSQLSERVER
- SQL Server Analysis Services - NT Service\MSSQLServerOLAPService
- SQL Server Reporting Services - NT Service\ReportServer
- SQL Server Integration Services 11.0 - NT Service\MsDtsServer110
- SQL Server Distributed Replay Client - NT Service\SQL Server Distributed Replay Client
- SQL Server Distributed Replay Controller - NT Service\SQL Server Distributed Replay Controller
- SQL Full-text Filter Daemon Launcher - NT Service\MSSQLFDLauncher
- SQL Server Browser - NT AUTHORITY\LOCAL SERVICE
In the past (SQL Server 2008 R2) the Agent, Engine, Analysis Services and Reporting Services would be blank and I'd specify the accounts I made. Before I got to this screen on the installation I had already made new user accounts, as domain accounts, but I see that the installer is pre-populating with local accounts.
In the end, should I let the installer make the accounts it wants to make or should I replace them with the accounts I've made?
I'm about to upgrade and consolidate a group of SQL Server 2008R2 to a single SQL Server 2012. I want have high availability and looking for the different options. The number of databases is fairly high (150+) so DBMirroring is out of the question.
Now I'm looking at "AlwaysOn Availability Group" and "AlwaysOn failover cluster" and I can't really figure out what way to go..... maybe even more options are available.
clustering might be a good way to do things, but it's really annoying to have a big power server doing nothing at all but waiting for the primary server to fail.
Is there any way to do real active/active clustering in SQL Server (real load balancing)?
I tried to install SQL Server 2012 Standard on Windows 2008 and on Windows 7 (I only wanted to install management studio on Win7). Same ISO; both machines are newly built. However, on Windows 7 Shared features directories are set to C:\Program Files... and greyed out even though none of the options are checked. C: is OS drive; however, it's a rather small SSD, so I am trying to install everything I can to another drive.
On Win2008 it is not greyed out (unfortunately, I don't need to change anything there).
What could cause Shared directories to be greyed out on Windows 7?
I'm aware that the SQL Server 2008 R2 Express was limited to 1 CPU and 10 GB Databases. It's not clear if Microsoft bumped those numbers up to be more reflective of 2012. I looked at several places but I still don't have a clear idea. Yes, I understand 2012 is not yet released but I have to assume it's software performance requirements are already set.