“Microsoft® System CLR Types for Microsoft® SQL Server® 2012” can be downloaded at Microsoft® SQL Server® 2012 Feature Pack (direct links: X86 version, X64 version).
And it seems to have fixed the installation problem for us; the server we needed to install the Report Viewer 2012 on does not have SQL Server installed at all.
that Microsoft has these optimized to work as good as a physical machine?
Yes, MS has - quite close.
The main problem is that it makes only sense in small installations. The moment your virtual SQL Server requires its own machine with a carefully laid out disk setup - which is any except a small SQL instance with low volume - there is nothing else to ...
This method seems to work:
The details in case that link goes bad:
There are no problems to add SQL linked server to the specific host
running it. But what if you need to give it an alias, rather than use
hostname as linked server name? Here is how to do it:
Why would you ask the internet about this?
There's so much WTF here, that I don't understand where to start!!
This question shows a fundamental lack of understanding of hardware, RAID arrays, storage, monitoring, and general IT best-practices.
I read this question and can't help but think:
Who is actually responsible for this server hardware? Where is ...
With RAID 5 you can only lose 1 disk and have your data remain available. You have lost 3 so you will need to rebuild the RAID and then restore the data from backup.
We have a canonical Q&A about RAID levels that may help your understanding.
Just for a sense of completeness I'll drop this in as an answer for future reference/searches.
Basically look at the VM's settings, then choose Resources, click on Memory and be sure that the 'Unlimited' box is ticked - leaving this unticked can cause needless ballooning.
There is no good rule of thumb.
The usefulness additional RAM depends very much on how your database is designed and the query patterns or your users. As an extreme example, if you have 1 TB of data in total, good indexing and 1000 simultaneous users that only ever go after 1 particular row (select * from dbo.BigTable where pkey_id = 42), you could get by ...
Revert the database back to multi user mode and try something like the following.
alter database xyz SET single_user with rollback immediate
Likely another process is grabbing the database connection before you get in there. Combining both statements should ensure you get that connection.
The error message is that the certificates were issued by an untrusted authority. That would be your AD domain, most likely.
A couple of workaround that you might want to try:
This dba.stackexchange.com post suggests clicking the options button on your connection window above and adding TrustServerCertificate=True under Additional Connection Parameters. ...
The problem occurs if a user has the same name as the PC or the domain.
You do not need to rename users however, you can simply not add that user to the list of sql server admins.
Note that the current user gets added by default so you have to remove it during installation.
During Installation, simply watch out for this step:
No, the SQL Server database engine does not include a Windows license. The Windows license would need to be purchased separately. Be careful which edition of Windows you purchase as different editions have different memory limits.
You don't need to add the whole table to a filestream filegroup, and indeed you can't, because only filestream columns get stored in filestream storage; other columns in the same table go to normal storage.
First of all, you need to choose which filestream filegroup you want to use to store the table's filestream data:
ALTER TABLE YourTable SET (...
Those three problems are all a result of the account running the SQL Service not being a domain account, and they will all be corrected by changing SQL to run under a domain account. Specifically:
A - an SPN is a Kerberos security feature that requires a domain account, and doesn't work with local accounts
B - In order to read from active directory, the ...
i had this problem and had to change the owner on the job to and sql account with the necessary permissions - > under SQL Agent > right click the job associated with your maintenance plan > Properties > Owner
If you later change the Maintenance plan the job owner changes back to your login so you have to go through this again.
According to this article (referenced originally by nopol's answer) it is possible to change the product key of a SQL Server 2008 installation by performing the following steps:
Open SQL Server Installation Centre
From the Maintenance screen choose Edition Upgrade
Enter the new new product key
It is also possible to change the product key at the command ...
Standard has more roles, like Domain Controller, File Server and all sorts of other enterprise roles.
Web has only Web Server, DNS etc, which is good for web hosting. Web is much cheaper, because is designed for scale-up, were you dont need a CAL for each visitor accessing the server via internet, while for the File Server in standard, you pay for each ...
Use firewalls - why on earth is that port (or any ports on an SQL server) open to the rest of the world?
Most business have multiple network tiers;
start with a firewalled/load-balanced web tier which has a firewall between it and the application tier allowing just the specific IPs and ports of known web servers in the web tier to talk to specific ...
KB888729: How to add processors to a computer that is running Windows Server 2003, Windows Server 2008, ... etc.:
When you restart the computer, Plug and Play detects and installs the
processor or processors.
All versions of Windows Server 2003, Windows Server 2008, Windows
Server 2008 R2, Windows Vista, Windows 7 and of Windows XP
As mentioned in other answers:
Old-style database mirroring and new-style AlwaysOn need threads and you will definitely run out of threads with 2000 databases. I vaugely recall that the practical limit is well below 200 databases. (There is a white paper on this somewhere, but I'm too lazy to look for it right now and this answer is already super-long.) Of ...
sys.dm_exec_requests E left join
sys.databases D on e.database_id = d.database_id
command in ('DbccFilesCompact','DbccSpaceReclaim')
I tried adding additional info to the answer by sphilp but that edit got rejected because some people seem to think it's incorrect. I can assure you: it is not.
What I wanted to add:
The Registered Servers functionality in SSMS can be used to connect to several servers in just a couple of clicks. If you group the servers together by creating a New Server ...
I have had this problem recently too and after mountains of research it appears to be common when a database is set to AUTO CLOSE. I set all the databases to AUTO CLOSE = FALSE. This started with one database then went over to two and the next it was on all of them. I simply restarted the SQL Server Instance Service instead of restoring databases. Another ...
If you aren't going to be using them anymore, delete them. Disabling them will have the effect of them not being accessible but if you are truly done with them, keeping your security dialog clean and master database clean of unused/unneeded logins makes sense.
Perhaps disable them for a week or so and make sure no jobs, no processes, no apps, etc. are using ...
By default SQL Server 2008 keeps the Built In Administrators group out of SQL Server access wise whereas in 2005 and below the Built In Administrators group was automatically granted SQL Server sysadmin rights.
As a local administrator you have a couple options though:
Restart SQL Server in single user mode (as described in this post: http://...
Regardless of what anyone here tells you, you really need to consult a license specialist on whatever products you're working with. Licensing is so complex these days that its way too easy to violate a license agreement.
That being said, if your intent is actually to use it as a dev server then I'd say use an MSDN license.
I agree with leaving it alone for now. SQL will try to load as much into memory as it can, up to the amount defined in MAX SERVER MEMORY. Your 600MB db will obviously fit into memory in your current config. Your server should have plenty of memory leftover without having to tweak SQL memory settings. Watch it as your database grows, though. (I'm not ...