22
Before adding a user one must first create a login.
Logins can only be created in the servers Security-folder (not in the databses Security).
So the login can be created under <server>/Security -> Right-Click -> New -> Login....
A user with the same name and settings will automatically be added to the databases selected in the User Mapping tab ...
18
Sorry to necro here, but just in case someone else hits this page with a similar question, and since there's so little documentation about this...
Short: The regular "Enterprise" (non-"core") edition caps the cores at 20, period. The "core" edition has no such cap. This is not a guess, it's a provable certainty. I ran into the specific question "when do I ...
8
I suspect that this article will help you out:
Understanding SSL Support
The protocol still uses TCP port 1433, by default, irrespective of SSL being used. The client can request SSL and, if the server has a certificate installed, the server and client will negotiate SSL. The server can be configured to force SSL, which will cause clients that do not ...
7
Back the whole system and the databases up and follow the upgrade instructions and you'll be fine.
7
I got the same error because I had left out the '/' in front of the ConfigurationFile argument. The correct syntax is something like this:
F:\setup.exe /ConfigurationFile=C:\setup\ConfigurationFile.ini
7
This TechNet article outlines the requirements and procedure for installing Microsoft SQL Server 2012 on Windows Server core. As you'll see, 2008 is not listed as a supported operating system for this. This is because the .NET Frameworks required for this to run are only supported on core editions of 2008 R2 and later.
5
Not only do they NOT tell you the difference between Enterprise and Enterprise Core. They have continued this practice of misnaming the downloads into SQL Server 2014. It is very easy to make a mistake and download the wrong version and wind up with a server with only 1/2 of it's cores working... Microsoft should make the following changes:
They should name ...
5
This sounds like a problem with your SQL Server topology.
It sounds like maybe you have Database Engine, Analysis services and client tools all on the SQL Server, but none of those features on the TFS server? If that's true, then you need to run the SQL Server setup on the TFS server (DEVSERVER) and install SQL Client tools on the TFS application tier, as ...
5
Have a look at this post which tells of a similar situation. The author used the SQL Native Client .msi from the \x64\Setup\x64 folder of the SQL 2008 distribution media. Maybe that will do it.
If not, you should be ok to uninstall the SQL Native Client 11, install v10 and then reinstall 11.
5
Auto shrink is evil.
You shouldn't be manually truncating the log files - if they're growing constantly then that's an indication that the database is using the FULL recovery model and you're not backing up the logs.
Depending on your recovery requirements, either start doing regular transaction log backups to keep the log file size down, or switch to ...
5
SQL Server will hold on to the RAM it allocates, so since it doesn't seem to go above 6-7 GB, I would allocate 8GB for SQL and keep 2-4 GB extra for the OS in this case (SQL always does some tasks outside the memory it allocates for sqlserver.exe.
It would be a good idea to put this value (8 GB) in the min memory settings for your sql server instance. This ...
5
SQL Server 2012 does not guarantee the order of rows returned in SQL 2012. Neither did 2000, for that matter. (The citation I found for that is actually 2005, but close enough.)
Essentially, the SQL Server Query Optimizer is guaranteeing that the
internal operator in the query tree will process its input in a
particular order. There is no ...
4
I finally received an answer directly from a very smart gentleman at Microsoft. I'll share the contents of our findings that don't have identifiable customer information in them:
The OpsManager database and SM DWStagingAndConfig database must have matching collations locales not necessarily the same exact collation as implied by some of the documentation.
...
4
If you can't access the distribution media, the installer for "SQL Server Native Client version 10.0" can be downloaded from the Microsoft SQL Server 2008 R2 Feature Pack. Expand the "Install Instructions" and search for "2008 R2 Native Client".
4
No. Not possible. Compatibility level talks of how the SQL behaves - not the database internal format.
I suggest you start standardizing your servers. THe requirement points to some highly disputable decisions - either to run outdated reserver machines, or to upgrade a production machine without planning.
4
Looks like it does.
http://blogs.technet.com/b/canitpro/archive/2013/08/20/step-by-step-creating-a-sql-server-2012-alwayson-availability-group.aspx
All editions of Server 2012 allow clustering.
4
The AlwaysOn feature (more appropriately called availability groups as "AlwaysOn" is the generic term for HA that also includes failover clustering) that you mention can be set up in a "share nothing" scenario. Which is to say that you don't need to have a SAN at all since the disks for each server can come from anywhere. You just need two 2012 enterprise ...
4
Since you're using a web role, I would assume that it is connected to your VNet by means of using a VPN gateway and a Point-to-Site tunnel, as stated here: https://azure.microsoft.com/en-us/blog/azure-websites-virtual-network-integration/
Here's the problem, the published information from Microsoft about their network speeds are as follow:
They never ...
4
Your transaction log backup is truncating the logs in the sense that it's making room in the existing log file for more transactions. If you want to shrink the log file, you need to choose the "shrink file" option in SSMS. Right click the database to find that option.
If the file size you shrink it to isn't large enough, based on how many transactions your ...
4
SQL DBA here. I think you are misunderstanding how sp_help_revlogin works: http://support.microsoft.com/kb/918992
It is a set of scripts you run on the source server, the output will be a big long script to re-create all logins, including (encrypted) passwords.
Take that script and run it on your destination server, it will re-create all logins, and your ...
3
This is poor design limitation, and it is still the case for SQL Server 2014. The SQL Server installer should be able to move everything!
However, you can work around it by creating folders where you want (still separate 32/64 bit), moving everything there from the original to the new, then creating junctions that map the new locations to the old. You'll ...
3
this is the link to SQL Native Client 10.0 (2008 R2) x64
http://go.microsoft.com/fwlink/?LinkID=188401&clcid=0x409
3
It looks like this is yet another case of Microsoft documentation being out-of-date and inaccurate. Excerpting from Clarification on SQL Server Collation Requirements for System Center 2012 from the System Center MSDN blog:
There has been quite a bit of confusion over the requirements for SQL
Server collation for the various components of System Center. ...
3
I had the same problem. After some research I found this page which suggests that this is caused by a race condition. Although the workaround given there wasn't applicable for me, after stopping every other debugging processes (Visual Studio) these annoying error messages didn't display anymore.
3
The answer provided by Cmosq seems more valid i.e. Core-Based Licensing and Server/CAL Licensing
This link provides some more info about the licensing related to major editions:
http://www.connectingup.org/donations/directory/328
The official naming is reasonably confusing!
3
If the failover is not happening, the first thing to check is whether AlwaysOn is really enabled. Perhaps the simplest way to test this is by looking in SQL Management Studio at the AlwaysOn Dashboard. Your Availability Group (AG) should have at least two active nodes. Does it indicate your AG is synchronized? Note that unlike previous HA solutions, the ...
3
What version of MSSQL are you looking at this for?
SQL 2012 HA options include AlwaysOn solutions which leverages Microsoft's failover clustering but adds functionality on top of it. Or you can setup log shipping to create a standby database. Technically, I think you can still do database mirroring in MSSQL 2012 but that is going to be deprecated in some ...
3
You cannot run SSIS package on a release that is below the developed level of the package, so it is not possible to deploy from SQL Server 2012 to SQL Server 2008 since SSIS packages are not backwards compatible.
This the SSIS engine issue.
See more here: Interoperability and Coexistence (Integration Services)
From the documentation:
On an instance of ...
3
Copying my answer from your StackOverflow question:
That is just the normal output for that cmdlet. To see QuorumType, you can use these methods:
$quorum = Get-ClusterQuorum -Cluster CLUSTER
$quorum | Select-Object *
$quorum.QuorumType
$quorum | Format-Table * # For display only
$quorum | Format-List * # For display only
Many cmdlets control which ...
3
If I understand your question, it sounds like you're looking for something like Transparent Data Encryption, in hopes of preventing a user detaching the database, attaching it to their own server, making changes, and re-attaching it to the original server. Transparent Data Encryption would require the user to have a certificate and a private key in order to ...
Only top voted, non community-wiki answers of a minimum length are eligible
