I have done a large number of SQL server implementations in recent years, both in on-prem datacenter and in Azure (IaaS). Now that SQL 2022 is available, I’ve taken a look at the differences compared to previous versions. Installing on Windows Server Core edition is also supported, so I take that scenario as a starting point.
As a basis, it is of course important that an Active Directory environment is available. In my demo environment I ran a domain controller in Azure based on Windows Server 2022 Azure Edition. This server provides the other servers with DNS. The domain is called ‘demo.lab’.
When you setup coexistence with Microsoft Exchange 2010 and 2013, you can manager you mailbox databases in different ways. Though the Exchange Management Console (EMC), Exchange Control Panel (ECP) or with Exchange Management Shell (EMS). Today I had to configure a new Microsoft Exchange 2013 environment in a existing Exchange 2010 environment, so this is a coexistence infrastructure.
When I had installed the new Exchange 2013 servers, and I had started the Exchange Management Shell (EMS) from the new Exchange 2013 server, I saw only the new Exchange 2013 database. But wait a minute, I had also a copple of mailbox databases configured on my existing Exchange 2010 environment. In the Exchange Control Panel (ECP), all the databases are visseble, but why not in the Exchange Management Shell?
The solution is pretty easy. Within Exchange 2013 there’s a new parameter that you can use with the Get-MailboxDatabase command. So the new parameter is -IncludePreExchange2013. The whole command should be: Get-Mailboxdatabase -IncludePreExchange2013.
Last week I was troubleshooting a RES Workspace Manager 2012 environment by one of our customers. A couple of times in one week, the datadisk of the SQL server was full, so at that time the SQL environment was not running anymore. The database of RES Workspace Manager was growing that fast….but why??
When looking for the actually size of the database, I saw that the size is just above the 20 GB. That’s pretty big if you ask me! The biggest data is the “logging” section. Okay…but which logging?? Sinds a few years, there’s a great tool available called DBLogCleanup. This tool has been written by Patrick van Grinsven and is extremely usefull for troubleshooting this kind of stuff.
Just run the tool, make a connection to your SQL environment and select the RES Workspace Manager database. At the log section, select “User Settings Sampling mode data“. As you can see, there were over the 16 million items in the database! The process iexplore.exe with the AppGUID 02222….6862 is growing realy fast!! So there’s a lot of User Sampling data in the database. After deleting the sampling data, the size of the database was 10 GB smaller.
1.) Run the DBLogCleanup Tool
2.) Fill in the SQL server, database, user and password
3.) Select the section you want to view
4.) Browse through the processes and note the AppGUID
5.) Open your RES Workspace Manager Console
6.) Navigate to your applications and find the specific AppGUID
7.) Open the properties of the application
8.) Navigate to User Settings and open the Sampling tab
9.) In the right corner hit “clear all sampled data”
10.) Make sure you turn off the sampling mode for that application
Conclusion:make sure you do not use sampling mode for a very long time! All the sampled data is stored in your database, so the database is growing very fast!!