Greetings fellow reader.
I’ve decided to start a series of posts about SQL Server, to tell, you about my experiences with SQL Server.
So, just to get started, let’s find out who is using my SQL Server, and what are they doing?
There are two ways to go about this. (Actually thee are more, but let’s start with these two!)
Open a query window in SQL Server Management Studio and type:
sp_who or sp_who2 the just press F5 or hit the Execute button.
The result will be a list of sessions with information about them, and you ca copy and manipulate in Excel.
Opening Activity Monitor
And checking the list of processes.
There we have a list of logins in use and there Session ID’s.
And there it is. Now we know who’s using our SQL Server box.
NOTE: The first 50 sessions are usually system sessions, but after SQL Server 2005, system sessions may pass that limit.
Ever looked at WSUS Server and found out you were running out of space, or, for some reason had to move the WSUS updates to another drive?
Well, here’s how you can do it:
First you need to be a member of the local admin group for that server, and create the new WSUS content folder on the new destination.
Then, open a command line and type:
wsusutil.exe movecontent DestinationDrive:”New WSUS Content Folder” DestinationDrive:”CreateLogFile.log”
(The wsusutil.exe tool is usually located in WSUSInstallationDrive:Program FilesMicrosoft Windows Server Update ServicesTools)
If you don’t want to copy the Content Folder files just add the -skipcopy optional parameter.
Nowadays, Windows identifies the majority of devices, but there are always devices harder to identify. When that happens you don’t need to get your tools and start unscrewing.
Just open Device Manager and identify the unknown devices.
Then open the device, select the Details tab and look for Hardware Ids property.
There you can get the Device ID and the Vendor ID, which we can look for in PCIDatabase website (http://www.pcidatabase.com/)
The result should be something like this:
Now you can look for the device driver knowing what you’re looking for.
I found this problem opening Exchange 2003 System Manager. When opening i I got the following error:
“Exchange detected that “C:windowssystem32mapi32.dll” is not the correct version required to
run Exchange System Manager or Exchange Server 2003. This may cause failures in Exchange System Manager,
affect availability of your server, or both. For more information see Microsoft Knowledge Base article
Q266418 at http://support.microsoft.com.”
To get around this I renamed the windowssystem32mapi32.dll, took the MAPI32.DLL from the Exchange
server CD-ROM (from the setupi386exchangebin folder) and copied it in to the windowssystem32 folder.
When you have a client in your Data Protector database that is no longer available, be it because you’ve reinstalled the OS without removing the agents, or because the machine simply died, you should clean up your client database.
For that, open the cell_info file with your preferred text editor and just delete the client line.
The cell_info file is usually located in the OmniBackConfigServercell folder.
I’ll be coming back to post some of my experiences as a SysAdmin.