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.
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 upgrading computers from Windows XP Professional to Windows 7 Professional but I have a problem getting one of the stock control software programs we use to connect to our SQL Windows Server 2008 R2 Standard from the new Windows 7 computers.
Our computers are connected to a domain and so is the SQL Server. The Windows XP computers allows each standard domain user to log on and connect to the SQL Server via the stock control software program.
But on the Windows 7 Pro computers standard domain users can't connect to the SQL Server but the domain administrator accounts on the same Windows 7 Pro computers can connect to the SQL Server via the stock control program.
I have setup the server alias, server name and port number via the SQL Server Client Network Utility (cliconfg.exe) so I know this isn't the problem as it works when I am logged on as domain administrator.
It seems to be something to do with domain user permissions and Windows 7 Pro. There seems to be a change from Windows XP Pro to Windows 7 Pro that doesn't allow standard domain users to connect to an SQL Server. But I can't find anything about this and can't workout how to fix it except to make all the users domain administrators which is obviously not a good thing to do. So basically I I think I need to create a group policy that allows the users to connect to the SQL Server but I have no experience doing this and don't know where to begin.
Thanks for all you guys help and I hope someone can provide me with the solution to this problem.
I have worked out that the UAC (User Access Control) is what was blocking the stock control program from connecting to the SQL Server.
I have two SQL Servers at two different servers:
SERVER 1: SQL Server Enterprise edition 2008 r2 64bit
SERVER 2: SQL Server Standard edition 2008 64bit
I have db_admin permission on both SQL Server, when I am connecting server 1 from server 2 then it is connecting(means connecting enterprise from standard) but when I am doing reverse it is not connecting. How can I resolve it?
Note: When I am connecting SERVER 1 from other servers with same SQL Server edition and vice versa, it is connecting well.
The edition is not going to be relevant if you are using SSMS. When you cannot connect, the problem is usually a configuration issues but if it works both ways to other servers, that might not be the case. Try the below first.
In the server properties dialog of Server 2, go to the Connections tab on the left. About 3/4 of the way down is an option to "Allow remote connections to this server". It should be checked.
If it is checked, the next thing to do is verify what port the server is on. If it is not on the standard 1433, you will need to add the port to the connection (e.g. MyServer,1234)
I'm writing a .NET app that connects to a remote hosted SQL Server. Researching hosts for when I roll this app out to multiple customers, I find that SQL Server 2008 R2 Web Edition is cheaper (monthly on a hosted dedicated server) than the Workgroup Edition and much cheaper than the Standard edition. Everything says Web Edition is for "website support" and "internet facing" use.
I know I must use Windows Server Standard and not Windows Server Web Edition to support database services, but what about the SQL Server version?
Simply - can a large number of users of a .NET Windows Forms program use a direct connection string to connect to SQL Server 2008 R2 Web Edition on the hosted server without going through a web server / browser?
Yes, it supports remote data connections.
Yes.
From my understanding of Web Edition, it is basically a mid-liner between Express and Standard. It's obviously not free, but it doesn't have the restrictions that Express does yet gives a lot of features (PBM, more than 1 CPU utilization, etc.).
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.