El conocimiento al alcance de todos.

Thank to: http://www.running-system.com/ MBR-initialized disks are limited to a maximum addressable storage space of 2 TB. Other limitations are that MBR only supports a maximum of 4 primary partitions. If you need larger disks and/or more partitions you have to change the layout to GPT. With GPT, the maximum configurations for Windows are: 128 primary partitions 18 ExaByte addressable storage space The challenge is, that it is not possible to change the layout to GPT with windows standard tools if the disk already contains data. If you right-click the affected disk (Computer Management – Storage – Disk Management) the option “Convert to GPT Disk” will be greyed out. In my case, the tool GPTGEN was the resolution.  It enables you to change the disk layout from MBR to GPT without downtime and data loss (nevertheless take care that you have a valid backup before you start!!!). You can download the tool eg. here:  Sourceforge.net – GPTGEN Before you can start, you hav

Thanks to: http://mssqllover.blogspot.com/ Issue: There are situations where a COM related error thrown while creating maintenance plan in SQL Server SSMS. Error Message: ======================================================================= ============================================================== Creating an instance of the COM component with CLSID {17BCA6E8-A95D-497E-B2F9- AF6AA475916F} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS) Step 1: Traverse to the C:\Program Files\Microsoft SQL Server\100\DTS\binn directory and run the Following from the command Prompt: REGSVR32.EXE dts.dll Step 2:   Once done with registering the dts.dll you will get an successful information. Step 3:  You have to close the SSMS and   which will solve the problem in creating the maintenance problem.     Maintenance plan will be created without any issues once the ab

Thank to: https://www.sherweb.com/ Hi Everyone!! There is one task I configure quite often as a Database Administrator…  setting up Database Mail to send an email if a SQL Server job fails . It isn’t difficult, but if you miss one step, it won’t work. Ugh!! I’ll list all the steps here so it can be done quickly and easily without losing all but one strand of hair on your head. Here are the steps: 1. Configure Database Mail. 2. Create a SQL Server job. 3. Adjust the properties within the SQL Server Agent. 4. Create an Operator. 5. Adjust the SQL Server job to send on Failure. Configuring Database Mail To complete this step correctly, a properly configured mail server is needed. In most cases it is okay to use localhost, but that requires the installation of Microsoft IIS/SMTP. If your administrator will not allow the install of IIS on a server running SQL Server, get the name of a mail server that can be used. Step. 1 Open  SQL Server Management Studio (SSMS) , c

Thanks to: https://www.petenetlive.com/ In this scenario I’m going to have two  VLANs , one for my wired clients, and one for a ‘Guest WiFi’ that I’m setting up. I want the guest  WiFi  to run in its own separate  VLAN , so it can’t touch my corporate network. And I want to  NAT  both networks to my public  IP . Maximum number of sub interfaces , depends on the hardware model maximum number of VLANs so; Model Max VLANS 5506-X 5 (30 with Security Plus) 5506-W-X 5 (30 with Security Plus) 5506-H-X 30 5508-X 50 5510 50 (100 with Security Plus) 5512-X 10 (100 with Security Plus) 5515-X 100 5516-X 100 5520 150 5525-X 200 5540 200 5545-X 300 5550 250 5555-X 500 5580 250 5585-X 1024 Note : Sub interfaces are  NOT  supported on the  ASA  5505. Solution To create sub interfaces on a physical interface, that interface must have no settings on it (other than it should not be shutdown). Petes-ASA # configure terminal Petes-ASA(config)# clear interface gig

Thank to: https://www.stellarinfo.com/ How to fix Recovery Pending State in SQL Server Database? SQL database states An SQL database is considered to be damaged if one or more of its core files are in the inconsistent state. Depending upon how severe the damage is, the database is marked with different states. Check the few states below: Online   – If one of the data files has been damaged during a query or some other operation, the database will remain online and accessible. Suspect   – If the transaction log is damaged and it prevents recovery or a transaction rollback from completing or causes it to fail. Recovery Pending   – If the SQL Server knows that database recovery needs to be run but something is preventing it from starting. This is different from the  SUSPECT state  because it can’t be said that recovery is going to fail – it just hasn’t started yet. The state an SQL database is in can be checked by running the following query: SELECT name, state_desc fro