System is Windows Server 2008 R2 Enterprise 64 bit
Running Microsoft SQL Server 2008 R2 (SP1) - 10.50.2425.0 (X64)
This is a newly built and deployed server, operating in an active/passive cluster. Dual Xeon procs, 64gb RAM, C drive is local Raid 1, all other volumes are DAS.
Often when I run perfmon, and click on the green plus icon to add counters, perfmon hangs for 3-4 seconds, and SQL Server hangs completely for about 60 seconds.
This is somewhat intermittent, but has happened 5 times in 2 days. perhaps half of the times I've run perfmon. I'm naturally hesitant to cause this issue purposefully as this is our production system.
Any thoughts?
This issue was caused by running the Community Technology Preview version of SQL Server 2008 R2 SP1.
Related
Until now we were Running a MSSQL 2019 Enterprise Server on Windows Server 2016. The MSSQL-Server is used for Business Intelligence, so it's also executing SSIS-Packages, stored in the Integration Services Catalog, using a SQL Server Agent Job. On the Windows 2016 Server this job took about 4 minutes for a regular refresh.
After switching to the new Windows Server 2019 it takes about 12 minutes, or three times slower. I already checked all settings of SQL Server and Databases. They all match the old setup. Disk, CPU and RAM also match and benchmarks show no issues. Also the new Server uses new Storage which is much faster than the old one. So it all comes down to Network Performance which seems to be far worse in Windows Server 2019 than 2016.
Does anyone have any idea what could be the issue here? I googled around and couldn't find any real solution to this. It seems like it's known that Win 2019 has less Performance than 2016. But the threads talking about this (without a solution) are several years old. I can't believe that this hasn't been resolved in the last 3 years.
Any help is appreciated.
Edit: Additional Explanation:
The SSIS Packages load Data from different locations. Another MSSQL-Server running on a Win 2016 Server and several Postgres-DBs running on Debian. The Data is stored on the mentioned SQL Server on Win 2016 (old) / 2019 (new) Server. Sure there are Lookups in the Packages. But the Packages are exactly the same. Also are the Databases, Tables, SQL Server Configuration and so on. The only difference is the Operating System. I'm exoecting the issue being around the Network Interface/Functionality of the OS because CPU, RAM, SSD are all ruled out because they are also identical and Benchmarks show no Issues. Also I noticed huge differences on Copying a 1GB File to the Servers using Remote-Desktop. The Copy on 2016 Server takes about 1:40min and on the 2019 Server 3:30min. Will do more benchmarks.
Update: I made additional tests. I wanted to know where exactly the ssis-Packages take longer to execute. So I made this setup: I installed Visual Studio 2019 Enterprise on both Windows Servers, the 2016 and the 2019 one. Then I copied the SSIS-Project to both machines and configured them to use the MSSQL-Database of it's localhost. Then I first executed single packages and then a larger Master-Package. After this I compared the Execution Times. And there was no difference. All packages executed in Visual Studio directly on the Server took almost the same amount of time.
Then I created a simple SQL Agent Job on both machines to execute the larger Master Package and only that. In Visual Studio the execution took about 2:40 minutes on both Machines. When I executed the same packe with the SQL Agent Job I got the following durations:
Windows Server 2016 with SQL Server 2019: 2:01 minutes
Windows Server 2019 with SQL Server 2019: 3:43 minutes
So the 2016 Setup was faster using the SQL Agent (which is reasonable because less overhead than the VS Execution), but the 2019 Setup was about 30% slower. As the Visual Studio Execution is virtualy the same than the SQL Server Agent Execution there has to be an issue with the SQL Server Agent causing it o be much slower as the one of the SQL Server running on Windows 2019. I have no idea what this could be.
We solved the mystery. Our environment is a ProxMox Virtualization Environment. The Harddisks of the SQL Server were mounted as SCSI. After we switched to SATA it got a huge increase in Perfomance. I don't know why because SCSI should be faster. All the drivers were up to date and the SCSI Controller was in Write Back-Mode. But this is an issue of our IT where I'm not involved. The reason for the drop in perfomance was because the old Server used SATA und the new one SCSI, as I said.
I am trying to figure out the best method for transferring SQL Server 2005 databases from 2 different physical servers to a new server running Windows Server 2008 64bit.
I own a fully registered copy of Microsoft SQL Server 2005 32bit Standard Edition. However all of my SQL Server databases together are only 4GB in size thereby making SQL Server 2008 Express an option.
Here is the breakdown of the servers:
(Old Server1) Windows 2003 Server 32bit - SQL Server 2005 Express 32bit
(Old Server2) Windows 2003 Server 32bit - SQL Server 2005 32bit Standard
(New Server) Windows 2008 Server 64bit - (Not sure which version to install)
The objective is to migrate the 2 SQL Server databases from Old Server1 and 1 SQL Server database from Old Server 2 to the New Server. What version should I install on the new server? Do I go with SQL Server 2008 Express or install the SQL Server 2005 Standard Edition?
Pending your response to which version to install, what are the correct steps to migrate (which I have never done before) the databases from both of these servers to the new server?
I have researched this online and I think this particular situation is unique in that I am transferring from both SQL Server Express and Standard from 2 different physical servers to a 2008 server that is 64bit. I cannot find anything online that I feel confident in trying. Please help me, as I have this migration deadline of this weekend. Any help is appreciated. Thanks
I tried to upgrade a failover cluster running SQL Server 2008R2 to SQL Server 2012 but the upgrade wizard reported a rule failure:
"The SQL Server and Analysis Services features of the selected clustered SQL Server 2005 instance have been installed into separate groups. SQL Server 2012 setup can only upgrade clustered instances installed in a single group. To continue, uninstall either SQL Server or Analysis Services before you upgrade."
Apart from the fact that the current cluster is running SQL Server 2008R2 (it wasn't even upgraded from 2005) both SQL Server and Analysis Services are in the same cluster resource group. The advice to uninstall one or the other is also unhelpful because adding/removing features on a failover cluster is not supported (see http://support.microsoft.com/kb/2547273).
Any suggestions would be appreciated.
Thanks
Graham
Have you slipstreamed all the latest service packs into the 2012 installer media?
If you're using RTM media there are loads of bugs in the setup program, good news is that this is now much easier to do in 2012 than it was in 2008:
Product Updates in SQL Server 2012 Installation
I thought R2 is a patch/service pack. I've been looking for a download but dont see one. I assume therefore that R2 is a new version, and that I would need the install media for sqlserver 2008 r2 to do an upgrade?
Also, would I need to pay for new licenses?
SQL Server 2008 R2 is a separate product. If you have bought your current SQL Server 2008 with Software Assurance (supplied by most software vendors who sell MS products), then you can upgrade at no cost.
Now for the fun part ... You'd think that doing an in-place upgrade from 2008 to 2008 R2 would be a snap. Be warned - it failed on me twice in a row. Luckily we had taken a VM clone and restored it as a test server first, to try out the upgrade. The two times it failed was for two different arcane reasons. The network guys were getting frustrated because they had to keep restoring a fresh test server from the clone. Be absolutely sure that you first test an in-place upgrade in a test environment before you touch your production server. When the in-place upgrade fails, it trashes your SQL 2008 instance and the final message from the installer is to uninstall and reinstall SQL Server. We just decided to instead do a clean R2 install on a new server. Extremely disappointing, since SQL Server is probably the most stable and reliable MS product.
I have a server machine with Windows 2008 Server R2 Foundation installed, that I use for hosting SqlServer 2008 service. There is no additional user registered on the OS, the clients asks only for connection with sqlserver. I've notice that periodically some clients stop working when trying to connect to sqlserver, while in the same time other clients are working properly. I know there are some limits on concurrent connections for foundation edition, but I can't understand which limit I'm breaking. Some ideas?
Windows Server 2008 Foundation limits include:
15 User Limit
50 TS Connections
50 RRAS Connections
10 TAS Connections
30 SMB Connections
1 socket systems only
8GB maximum memory support
No virtualization use right
from: https://msmvps.com/blogs/bradley/archive/2009/08/05/windows-server-2008-foundation.aspx
You can run sp_who and see all the connections that are being used but based on my understanding 30 is the limit.