My SQL Server 2012 is using 4-20% of my i7, but I don't have any application using SQL Server. This is Enterprise installed on a Win 7 box I use for development. I thought maybe it was just updating statistics or something but hours later it is still using the CPU for something. Can someone please help me figure out what background processes might be running. I don't have SQL Agent installed. Just the engine, integration services, and the Management Studio.
Did you check sys.sysprocesses for any running processes.
Related
Recently I have installed sql server then was not able to create sql server integration project using sql server integration import project wizard.so uninstalled Visual studio, sql server data tools.
Now I have installed visual studio 2019. which was installed successfully and then started to installed sql server data tools. Which downloaded successfully and stuck after 80% of installation.
Please check below screenshot
After 5 hours, I looked in task manager and I don't know how their were 2 .exe was running.I changed priority to high for first one and ended second .exe task and sql server data tools installed successfully.
An alternate answer.
My corporate antivirus was likely fighting with the ssis Installer. After watching each of the executables peek the cpu on my machine back and fourth for 60 minutes and trying a reboot..ect.. I decided to disconnect from the internet.
This seemed to calm the security software and allow the installer to do it's thing.
I have installed SQL Server 2019 CU2 and after that SQL Server Agent start is consuming too much CPU resulting into skip job schedules.
Although the agent service is running but it looks like hang and didn't process / kick off any jobs.
Once I re-start the Agent service it starts working again (cpu = 0), but then after some time 1-2 hours CPU intake in high and jobs do not run.
Is anybody else facing same issue with SQL Server 2019 CU2?
Any help would be much appreciated.
Thanks,
There is already a thread for this on DBA StackExchange. The issue was introduced in CU2 and will be fixed in CU3. If you're facing this, the workaround is to revert to CU1 until you are able to upgrade to CU3.
In our company we have to support a large legacy system built on Microsoft Access 2010 as frontend and SQL Server 2008 R2 as backend. The backend SQL server runs on Windows Server 2008 R2. Currently our users works on Terminal Server sessions on a Windows Server 2008 R2. A couple of days ago we started to test Windows Server 2019 and Notebooks with the latest version of Windows 10. We recognized a big performance difference while executing the same Access databases on the different environments.
For instance the creation of a report takes 27 seconds (new environment) instead of 7 seconds (old environment). The database.accdb is identical, the backend is identical (still Windows 2008 R2 Server with SQL Server 2008 R2 and SP2), only the execution environment (Windows) changed.
Does anyone of you have an idea how to explain this?
In Access 2010 the SQL server tables are linked using System-DSN data sources. On the old environment ODBC is used (Driver: SQL Server, Version: 6.01.7601.17514).
On the new environment I tested the following drivers:
ODBC Driver 11 for SQL Server (2014.120.5543.11)
ODBC Driver 17 for SQL Server (2017.173.01.01)
SQL Server (10.00.17763.01)
SQL Server Native Client 10.0 (2009.100.4000.00)
SQL Server Native Client 11.0 (2011.110.5058.00)
I created a new System-DSN using the different drivers and updated the linked tables in Access. But in any case the performance is still bad. I also tested the latest version of Access which comes with Office 2019, but again it is slow.
Sounds like your terminal sessions are getting throttled. Despite the fact that you have a SQL Server back end, Access is still doing a fair bit of thunking with the result sets, so any resource throttling differences between your Server 2008 and Server 2019 policies could be choking Access in the new server.
I think your answer is going to be found in Windows System Resource Manager. The page says it's not being maintained, but following the "Recommended Version" link leads to a generic Server 2019 page. Here's another article about how WSRM might be throttling sessions: Using WSRM to control RDS Dynamic Fair Share Scheduling.
Compare the Weighted_Remote_Sessions policy in 2008 and 2019 servers. There's either been a change to the default settings or behavior or the 2008 server policy was modified in the past to get to the current performance level.
Ok, a number of things to check.
First thing to check:
Launch the ODBC manager and check if SQL log tracing is on. I don’t know why, but I see sql logging turned on.
You NEED to be 100% sure it is turned off.
You MUST launch the ODBC manager from the command line or start menu, since the one in the control panel is for the x64 bit version, and you are using Access x32 (I assume).
So launch this version:
c:\Windows\SysWOW64\odbcad32.exe
So VERY important to launch the x32. It is assumed you are using a FILE dsn. So check these two settings:
(Make sure they are un-checked).
Next up?
Link access using the IP address of the sql server.
So, place of say:
myServer\SQLEXPRESS
Use:
10.50.10.101\SQLEXPRESS
(Of course use the IP address of sql server, not the above “example” IP).
The above things are quite easy to check.
Still no performance fix?
Then disable the fire wall on your new Terminal server (I seen this REALLY cause havoc).
And, disable windows defender on the new TS server if running.
The above tips should fix your issues.
If above don’t work, then next would be to check the priority settings for the TS server (GUI over server).
However, I am betting the above checks should restore your performance.
I want to set up a Replication between two different computers that run MS SQL Server 2008, the master runs on Windows Vista, and the slave will run on Windows XP.
I´ve done this before between two MySQL-servers.
Question: Does anyone have a guide for **Replication in MS SQL Server 2008**?
I found this site to be helpful setting up Replication you may have already seen it but in case you haven't:
https://www.sqlshack.com/sql-replication-basic-setup-and-configuration/
I have settled a web synchronization between SQLSERVER 2005 as publisher and SQLEXPRESS as suscriber. Web synchro has to be launched manually through IE interface (menu tools/synchronize) and to be selected among available synchronizations.
Everything is working fine except that I did not find a way to automate the synchro, which I still have to launch manually. Any idea?
I have no idea if this synchro can be launched from SQLEXPRESS by running a specific T-SQL code (in this case my problem could be solved indirectly).
Denny Cherry, a SQL Server MVP, is writing a replacement for SQL Server Agent.
Denny's blog about it
His Standalone SQL Agent project on Codeplex
Using this, you would be able to automatically initiate code on a scheduled basis. But it's either this, or writing your own .NET app to kick off jobs. SQL Server Express Edition doesn't include any kind of automated job scheduling.
I don't really know about SQL Server web synchronization, but as SQL Express don't have an SQL Server Agent, you can write a C# console application that runs with the scheduled tasks.