logman export -n "Server Manager Performance Monitor" -xml SMPM.xml
- Open up the generated XML file and remove the entire section List of IDs then save the file.
- Open an elevated command prompt where the data collector set is missing and import the XML file:
logman import -n "Server Manager Performance Monitor" -xml SMPM.xml
logman start "Server Manager Performance Monitor" https://www.itprotoday.com/windows-78/fixing-missing-performance-counters-server-manager
I recently implemented an AWS site-to-site VPN for a customer to connect their on-premise network to their newly deployed AWS account.The requirement was network level connectivity from their on-pr…
This article will help you understand the detail information of each component when we backup under System State:
· Active Directory DC Database file (ntds.dit)
· Boot and System protected files
· COM+ Class registration database
· Registry info
· SYSVOL folder and its files
· IIS metabase
· Cluster service info (on cluster node only)
The script that is discussed in this section opens the firewall ports for SQL Server.
To create the script, follow these steps:
- Start Notepad.
- Copy and paste the following code into Notepad:
netsh advfirewall firewall add rule name="Open Port 80" dir=in action=allow protocol=TCP localport=80 @echo ========= SQL Server Ports =================== @echo Enabling SQLServer default instance port 1433 netsh advfirewall firewall add rule name="SQL Server" dir=in action=allow protocol=TCP localport=1433 @echo Enabling Dedicated Admin Connection port 1434 netsh advfirewall firewall add rule name="SQL Admin Connection" dir=in action=allow protocol=TCP localport=1434 @echo Enabling Conventional SQL Server Service Broker port 4022 netsh advfirewall firewall add rule name="SQL Service Broker" dir=in action=allow protocol=TCP localport=4022 @echo Enabling Transact SQL/RPC port 135 netsh advfirewall firewall add rule name="SQL Debugger/RPC" dir=in action=allow protocol=TCP localport=135 @echo ========= Analysis Services Ports ============== @echo Enabling SSAS Default Instance port 2383 netsh advfirewall firewall add rule name="Analysis Services" dir=in action=allow protocol=TCP localport=2383 @echo Enabling SQL Server Browser Service port 2382 netsh advfirewall firewall add rule name="SQL Browser" dir=in action=allow protocol=TCP localport=2382 @echo ========= Misc Applications ============== @echo Enabling HTTP port 80 netsh advfirewall firewall add rule name="HTTP" dir=in action=allow protocol=TCP localport=80 @echo Enabling SSL port 443 netsh advfirewall firewall add rule name="SSL" dir=in action=allow protocol=TCP localport=443 @echo Enabling port for SQL Server Browser Service's 'Browse' Button netsh advfirewall firewall add rule name="SQL Browser" dir=in action=allow protocol=UDP localport=1434 @echo Allowing multicast broadcast response on UDP (Browser Service Enumerations OK) netsh firewall set multicastbroadcastresponse ENABLE
- Save the file as a .txt file by using the following name: OpenSqlServerPort.txt
- Rename the OpenSqlServerPort.txt file to the following: OpenSqlServerPort.bat
Before you run the OpenSqlServerPort.bat script, you must copy the script to the computer that has the firewall and then run the script on that computer. To run the script, follow these steps:
- Click Start, click Run, type cmd, and then click OK.
- At the command prompt, use the cd command to move to the folder in which you saved the OpenSqlServerPort.bat file.
- To run the OpenSqlServerPort.bat script, type OpenSqlServerPort.bat at the command prompt, and then press Enter.
Recently I have been working with a client who has a production SQL Server instance that has ~2.5k databases on it. They are in the process of moving to a new SQL Serve cluster and are reviewing their other non-production environments too.
One of their major pain points at the is their pre-production refresh process, this involves restoring all 2.5k databases to a pre-production SQL Server instance. The current process involves retrieving backups from Iron Mountain and performing file system restores. They are looking to streamline this process and automate it as much as possible. Most of the process could be achieved using T-SQL, but there are extra file system tasks that need to be performed which are more easily achieved using PowerShell. PowerShell 4.0 brought us the Restore-SQLDatabase cmdlet and so it was worth evaluating this to see if I could encapsulate the entire thing in one script. It’s…
View original post 382 more words