We recently moved from the following server: Windows Server 2008 R2 + MSSQL 2008 R2 STD to Windows Server 2012 R2 +MSSQL 2016 STD. In terms of hardware, the old server was 1271v3 with 24 GB memory and the new server is 1271v6 with 32GB of memory. The rest of the hardware of the two servers is the same. The db was transferred using db backup and restore.
Although everything is working on the new server with no errors, it is significantly slower than the original server and we are even seeing some deadlocks.
If everything is the same or newer/better, how can this be?
The problem was not SQL server at all. The new server was using the default Windows power plan which is "Balanced". Switching the plan to "High Performance" mode caused a performance increase of up to 300% on more complex and long running queries.
Related
We have 8 instances out of which 6 are SQL Server 2014, 1 is SQL Server 2017 and all servers are running on Windows Server 2012 R2. The min and max memory set correctly for SQL Server 2014 & 2017. However, one of our DBAs enabled lock pages in memory for SQL Server 2017, but rest do not have this counter enabled.
There is one instance which sometime run into a problem "insufficient memory to process the thread" on same box.
What would be the recommendation for lock pages in memory for server with multiple instances? Should we enable it or not, even if we set min and max memory correctly.
I am investigating the impact of upgrading from SQL Server 2008 R2 to SQL Server 2012. To reduce the immediate impact of migration, I am planning to set the database compatibility to SQL Server 2008.
Does anyone know if there is an impact on performance of queries and other DML operations compared to setting the database to SQL Server 2012?
I have SharePoint Foundation installed.
Also I have install SQL express 2008.
I had 4 GB limit.
After some time I have spent almoust all free space.
Next, I have install SQL express 2008 R2 (R2 should give me 10 GB limit for database).
I want to check if everything is ok, but I do not know where to check free size.
I can check how much I have spent, but I can not check how much space I still have.
Can someone help.
Thanks!
There is no way to check the database size limit directly, however the version of SQL Server Express determines the limit. SQL Server 2008 R2 Express or newer will allow up to 10 GB of database size, while earlier versions allow only 4 GB.
If you are still in doubt, and want to confirm your instance of SQL Server 2008 R2 Express allows 10 GB databases, just create a new database and insert a bunch of data into it.
We have a Windows 2008 Server R2 Enterprise x64 with 32gb.
We are also still using SQL Server 2000 Enterprise.
I have been monitoring the memory usage and it is only using 17.3GB total.
I have set SQL server to use AWE with a max memory usage of 29gb.
Any ideas how to allow/get SQL server to use the extra ram?
Thanks
The reason it is not using all memory is because it doesn't need it.
SQL Server is very good at managing it's own memory. The sizes of the databases you gave, fit into 11GB of RAM, that leaves 6.3 GB for internal structures such as buffers, plan cache etc. (more than enough).
We have an analytics database server running SQL 2008 R2 with 192 GB of physical RAM. However, we're noticing that during analytics process, the server only uses around 70 GB, but tempdb swells to 300+ GB. The current Maximum Memory is set to 2147483647 MB. The server is running Windows 2008 R2. Is there a way to make SQL Server use more RAM and less disk-based tempdb?
I figured out what is going on. We're currently using the Standard Edition of SQL Server 2008 R2, which, apparently, can only use a maximum of 64 GB of RAM.
http://msdn.microsoft.com/en-us/library/ms143685.aspx