If you think you are then take this Redmond Magazine Quiz and see where you rank in the ‘Schema’ of things.
http://redmondmag.com/features/print.asp?EditorialsID=618
You will be ranked according to points and will qualify as one of the following:
Domain Controller
Human Firewall
Tech Plugger
Security SlackerIT Idiot
This Vbs script will take a print server name supplied from an Input box and send the following information to an Excel spreadsheet:
Print Server Name, Share Name, Comment, Driver Name, Job Count, Location, Port Name, Published, Queued, Shared and status
Vbs Script:
strComputer = InputBox("Enter Print Server Name")
Set objExcel = CreateObject("Excel.Application")
objExcel.Visible = True
objExcel.Workbooks.Add
intRow = 2
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")
Set colItems = objWMIService.ExecQuery("Select * from Win32_Printer",,48)
objExcel.Cells(1, 1).Value = "Name"
objExcel.Cells(1, 2).Value = "Share Name"
objExcel.Cells(1, 3).Value = "Comment"
objExcel.Cells(1, 4).Value = "Driver Name"
objExcel.Cells(1, 5).Value = "Job Count"
objExcel.Cells(1, 6).Value = "Location"
objExcel.Cells(1, 7).Value = "Port Name"
objExcel.Cells(1, 8).Value = "Published"
objExcel.Cells(1, 9).Value = "Queued"
objExcel.Cells(1, 10).Value = "Shared"
objExcel.Cells(1, 11).Value = "Status"
For Each objItem in colItems
Select Case objItem.DetectedErrorState
Case 0 Status = " Online"
Case 1 Status = "Paused"
Case 2 Status = "Pending Deletion"
Case 3 Status = "Error"
Case 4 Status = "Paper Jam"
Case 5 Status = "Paper Out"
Case 6 Status = "Manual Feed"
Case 7 Status = "Paper Problem"
Case 8 Status = "Offline"
Case 256 Status = "IO Active"
Case 512 Status = "Busy"
Case 1024 Status = "Printing"
Case 2048 Status = "Output Bin Full"
Case 4096 Status = "Not Available"
Case 8192 Status = "Waiting"
Case 6384 Status = "Processing"
Case 32768 Status = "Initializing"
Case 65536 Status = "Warming Up"
Case 131072 Status = "Toner Low"
Case 262144 Status = "No Toner"
Case 524288 Status = "Page Punt"
Case 1048576 Status = "User Intervention"
Case 2097152 Status = "Out of Memory"
Case 4194304 Status = "Door Open"
Case 8388608 Status = "Server Unknown"
Case 16777216 Status = "Power Save"
Case Else Status = "UNKNOWN"
End Select
objExcel.Cells(intRow, 1).Value = objItem.Name
objExcel.Cells(intRow, 2).Value = objItem.ShareName
objExcel.Cells(intRow, 3).Value = objItem.Comment
objExcel.Cells(intRow, 4).Value = objItem.DriverName
objExcel.Cells(intRow, 5).Value = objItem.JobCountSinceLastReset
objExcel.Cells(intRow, 6).Value = objItem.Location
objExcel.Cells(intRow, 7).Value = objItem.PortName
objExcel.Cells(intRow, 8).Value = objItem.Published
objExcel.Cells(intRow, 9).Value = objItem.Queued
objExcel.Cells(intRow, 10).Value = objItem.Shared
objExcel.Cells(intRow, 11).Value = Status
intRow = intRow + 1
Next
objExcel.Range("A1:K1").Select
objExcel.Selection.Interior.ColorIndex = 19
objExcel.Selection.Font.ColorIndex = 11
objExcel.Selection.Font.Bold = True
objExcel.Cells.EntireColumn.AutoFit
Set objExcel = Nothing
Set objWMIService = Nothing
Set colItems = Nothing
Use this SQL query to find machines in your SMS database that are Obsolete along with information about the obsolete client machine(s)
SQL Query:
Select
SD.Netbios_Name0 Name,
'Obsolete' = Case
When SD.Obsolete0 = 1 Then 'YES'
Else 'NO'
End,
'Active' = Case
When SD.Active0 = 1 Then 'YES'
'Client' = Case
When SD.Client0 = 1 Then 'YES'
'Client Type' = Case
When SD.Client_Type0 = 0 Then 'Legacy Client'
When SD.Client_Type0 = 1 Then 'Advanced Client'
Else 'Device Client'
SD.Client_Version0 'Client Version',
'Decommissioned DDR Set' = Case
When SD.Decommissioned0 = 1 Then 'YES'
SD.Hardware_ID0 'Hardware ID',
SD.User_Domain0 'Account Domain',
SD.User_Name0 'Last Logon User Name',
SD.Operating_System_Name_and0 NOS,
SD.Resource_Domain_Or_Workgr0 'Resource Domain',
SD.Sms_Unique_Identifier0 'SMAS Unique Identifier',
Convert(Char(101), WD.LastHwScan) 'Last Hardware Scan Date',
Convert(Char(101), CS.TimeKey) 'Last Computer Time Stamp'
From System_Disc SD
Join WorkstationStatus_Data WD On WD.MachineID = SD.ItemKey
Join Computer_System_Data CS On CS.MachineID = SD.ItemKey
Where (SD.Obsolete0 = 1 AND SD.Active0 = 0)
In SMS 2003 there are actually three service accounts and they are required accounts and are automatically created by the SMS installation process depending on the security mode that you have selected.
There is the SMS service account, the local system account and the remote service account. The accounts seem to be similar but they are not. Some have more rights, privileges and responsibilities than the others and as such they perform separate tasks. However the service accounts do have something in common in that they are created by the SMS site server installation process.
The familiar SMS service account (SMSService) is a standard security account as in SMS 2.0 and it provides access to SQL server if you are using windows authentication as well as creates SMS site server directories and copies files as well as well as installs and verifies that services are operating as expected. It also provides the security context that the SMS executive service runs on. It can also access domain controllers (DC’s) when it needs to get information about users, groups, computer accounts and Active Directory (AD) containers.
Notes: It is important to create additional optional accounts within SMS 2003 such as the site system connection account however if you do not create one your SMS site server will use the SMS service account as the sites site system connection account. You can also specify or use the SMS service account as your sites site address account if need be. However it is recommended that you create a site system connection account and a site address account and let the SMS service account manage the site server services.
The local system account (Local) as well as the Computer account on your site server is created and used when you are running in advanced security mode It serves as the SMS service account. It runs the SMS services as well as makes changes to the server and makes use of computer accounts as opposed to user accounts to connect to clients and other servers running SMS components. The local system account is primarily intended to maintain communications and run services and their related tasks.
The Remote service account (SMSSvc_xxx) where xxx is your three letter side code is created automatically when you assign the Client Access Point (CAP) role to a remote site system. It is primarily designed to run on remote SMS site systems and services the SMS executive services on the CAP other than the site server or on a remote server. It like the SMS service account handles SQL server if the SQL monitor is running on the remote site system as well as the processes necessary for the operations on the CAP. Your local system account serves these functions when running in advanced security mode.
Most computer workstations in a Windows NT domain are Microsoft Domain Name System (DNS) clients and as such they store or cache name resolution lookup request searches locally to speed up name resolution on the network.
Sometimes while on the internet or on the Local Area Network (LAN) your client(s) may get a bad DNS entry. If you do not want to wait for the DNS cache to automatically remove this entry you can delete or flush it manually from the command prompt using IpConfig.
To flush the DNS resolver cache manually from the command prompt enter the following:
IpConfig /FlushDns
You will then be presented with the following:
Windows IP Configuration
Successfully flushed the DNS Resolver Cache.
To view your DNS resolver cache from the command prompt enter the following:
IpConfig /DisplayDns
In my post entitled “Testing and backing up is (not) hard to do” I expressed the need for people to test or create database copies and backup their databases to avoid data loss. In that article I focused on SMS 2003 and now I would like to turn my focus onto SQL 2005.
As I mentioned in the previous post the SMS 2003 database and backup procedures are not much different than its predecessor. The same can be said of SQL 2005 because it is not much different that its predecessor for creating test databases.
Note: To create a test database you can also refer to the previous articles links for my posts from the past.
The first step is to create the database. There are however several ways to create a database. You can use a SQL query or a script such as a WMI or Vbs script or simply import an existing databases data into a new database “shell”
The easiest way to accomplish this is to use the SQL Server Management Studio interface by right mouse clicking on the databases folder from the object explorer and select New Database. At this point the new database wizard is started and brings up the new database screen.
From the general tab you specify the database name as well as the owner of the database. The database files is where you specify additional options such as the initial size of the database and can set the autogrow properties for the newly created database.
On the options tab you set the collation, recovery model and set the compatibility level. You are also given the chance to further fine tune the database by modifying the other options from the bottom pane. In the final tab you find the filegroups screen for the database.
Note: If you want to see how the existing SMS or MOM database is set right mouse click the database and select properties and the database properties screen will be displayed providing you with all that databases configuration.
Once you have your database shell created and configured you need to create the tables to put your captured or manually entered data into. If you simply want to make a copy of your SMS or MOM database there is no need to create the tables manually with SQL 2005. You can simply use the copy database option from the task menu and you will have an exact copy of the existing database as a new database on your test server.
The easiest way to create a new table in your database is to use the new table wizard which is found when you select your database and right mouse click on tables and select new table to begin the new table wizard.
First you enter the name of the new table in the Column name row and then tab over and set the Data type for the column. By default the Allow nulls is check but you can uncheck the box if you do not want that option set. Continue doing so until all the tables you require are created.
How can I modify this script to prompt for the Computer Name and for the New console folder name and let me know when it has finished.
set objSWbemLocator = CreateObject("WbemScripting.SWbemLocator")
set objSWbemServices= objSWbemLocator.ConnectServer _
("COMPUTER NAME", "root\sms")
Set ProviderLoc = objSWbemServices.InstancesOf("SMS_ProviderLocation")
For Each Location In ProviderLoc
If Location.ProviderForLocalSite = True Then
Set objSWbemServices = objSWbemLocator.ConnectServer _
(Location.Machine, "root\sms\site_" + Location.SiteCode)
End If
Set objNewConsoleFolder = objSWbemServices.Get("SMS_ObjectContainerNode").SpawnInstance_()
objNewConsoleFolder.Name = "Hardware - Disk"
objNewConsoleFolder.ObjectType = 8 ' Report Node.
objNewConsoleFolder.ParentContainerNodeID = 0 'Create in root node.
objNewConsoleFolder.Put_
strServerName = InputBox ("Enter Reporting Server Name")
strFolderName = InputBox ("Enter Report Folder Name")
Set objSWbemServices= objSWbemLocator.ConnectServer (strServerName, "root\sms")
objNewConsoleFolder.Name = strFolderName
objNewConsoleFolder.ObjectType = 8
objNewConsoleFolder.ParentContainerNodeID = 0
Wscript.Echo "Done"
I have been watching the Simpson’s cartoon on FOX for several years now and I don’t think there are too many from recent years that I have not seen.
I have seen many Simpson’s Images and Video clips as well as listened to many Audio clips many of which were on the risqué side over the years. This however is the first time that I have seen what I would consider a good live action representation of the Simpson’s cartoon intro.
I hope you enjoy it as much as I did … at least the first dozen times I watched it …
View On YouTube
http://www.youtube.com/watch?v=49IDp76kjPw
Download From EbaumsWorld
http://www.ebaumsworld.com/2006/07/real-life-simpsons-intro.wmv
Pluto use to be our solar systems ninth Planet and the farthest from the sun but now it is no longer deemed a planet because it is simply too small. It is still a planet but now it is a “Dwarf Planet” along with the asteroid Ceres and an object named UB 313 (Zena) which incidentally is larger than Pluto which is only a mere 2,360 Km or 1,467 miles in diameter and smaller than most moons.
In Prague (Czech Republic) on August 24th 2006 it was determined by the general assembly of the International Astronomical Union (IAU) in their twenty-sixth annual (August 14 -25 2006) General Assembly that Pluto is a dwarf planet in resolution 5A that they passed.
The IAU is a group of 2500 scientist from around the world and was founded in 1919 and has included some of the best minds of recent generations however as an amateur astronomer since I was in Boy Scouts I feel this is a great loss.
Now we only have 8 planets in our little solar system and Neptune is the farthest planet from the sun and all the technical books have to be rewritten dealing with astronomical fact and all the little school children have one less planet to memorize and be tested on.
The icy and rocky Pluto was the only planet to be discovered in the United States (Flagstaff, Arizona) in 1930 by Clyde Tombaugh. He named it after the Roman god of the Underworld in keeping with the tradition for naming planets. Pluto may be small but until now it was the coldest planet in our solar system at negative 287 degrees Fahrenheit.
For the record a dwarf planet is a celestial body that:
(A) Is in orbit around the sun,
(B) Has sufficient mass for its self-gravity to overcome rigid body forces so that it assumes a hydrostatic equilibrium (nearly round) shape,
(C) Has not cleared the neighborhood around its orbit, and
(D) Is not a satellite.
Sadly by these new definitions Pluto is in fact a dwarf planet.
SharpReader Version 0.9.7.0 is a freeware RSS Aggregator for Windows created by Luke Hutteman and is available for download at http://www.sharpreader.net
Not only is this a very clean and tidy almost Microsoft looking newsreader applet but it is small and simple to use for reading myItforum and other blogs as well as reading Microsoft TechNet Security Bulletins. I have been using it for some months now and one of the things I like best about it is there is no need to “Install” it. I simply expanded the zip file into a directory on my computer and use it from there.
It has all the standard features you need to easily view your news feeds such as allowing you to organize your news feeds into categories and you can view feeds without having to subscribe to them first. With its drag and drop capability it is also quick and simple to use when viewing feeds that you may or may not want to subscribe to.
It also places an icon in the taskbar and notifies you when new content from one of your subscriptions is added. You can also tell the applet how often to look for new content or keep the default value of 1 hour. You can also filter your content by time as well as search for keywords in your subscriptions.
The website also allows you to download plug-ins for w.bloggar and BlogThisUrl among others. It also comes with plug-in integration for Atom, Feedster and Technorati.
SharpReader Screen Shots
http://www.sharpreader.net/screenshots.html
Version 0.9.7.0 Installer Download
http://www.sharpreader.net/SharpReader0970_Setup.exe
Version 0.9.7.0 Zip File Download
http://www.sharpreader.net/SharpReader0970.zip
For a free and clean looking simple to use RSS Aggregator SharpReader is a good choice. SharpReader may not have all the bells and whistles of other free aggregators that others are using or touting such as Rss Bandit, Rss Reader and Feed Reader but because it is not an MSI based install I like it just fine. I would suggest it to you if you are new to RSS news feed reading or just want a simple Aggregator to receive and view TechNet security bulletins.
Microsoft TechNet Security Bulletins
http://www.microsoft.com/technet/security/bulletin/secrss.aspx
Beginning with Microsoft Windows 95 Microsoft introduced the "Speech Application Programming Interface" (SAPI). Applications that use SAPI include Microsoft Office, Microsoft Agent and Microsoft Speech Server among others.
Version History:
SAPI 1.0 - 1995
SAPI 2.0 - 1996
SAPI 3.0 - 1997
SAPI 4.0 - 1998
SAPI 5.0 - 2000
SAPI 5.1 - 2001
SAPI 5.2 - 2004
SAPI 5.3 - Expected to ship With Windows Vista
Note: Windows XP and Windows Server 2003 come with Microsoft Sam but you can also download Microsoft Mary and Microsoft Mike. To find which ones you have installed you can run this Vbs script:
Set objVoice = CreateObject("SAPI.SpVoice")
For Each strVoice in objVoice.GetVoices
Wscript.Echo strVoice.GetDescription
Note: It is important to note that the scripts below will execute and read your default speech as specified in the Windows XP and 2003 Servers control panel. You can find this by looking at the speech properties and checking the Text to speech voice selection name that you have specified.
Dim strText
'WarGames
strText = "Shall We Play A Game ?"
Set Sapi = Wscript.CreateObject("SAPI.SpVoice")
Sapi.speak strText
strText = InputBox("Enter Text To Speak")
Const ForReading = 1
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objText = objFSO.OpenTextFile("MyTextFile.Txt", ForReading)
strText = objText.ReadAll
objText.Close
Web Page Links
Microsoft Speech Home Page:
www.microsoft.com/speech
Microsoft SAPI 5.1 SDK:
www.microsoft.com/speech/download/sdk51
Microsoft SAPI 5 Engine
http://download.microsoft.com/download/speechSDK/SDK/5.1/WXP/EN-US/speechsdk51.exe
Active
This data type is initially set to 1 (Yes) and is set to 0 (No) when the client health tools determines that the client failed its checks and finds that the client is either not in a healthy state or is no longer on the network.
Obsolete
This data type is initially set to 0 (No) and is set to 1 (Yes) when the site server determines that the client hardware ID has been updated or superseded by another record for the machine. If multiple records are in place having the same hardware ID value for the machine then the older records are then marked as obsolete.
PreviousSMSUUID
When the computer determines that the machines hardware has changed dramatically a new GUID is created for the computer and it marks the old record and the old GUID as obsolete.
SD.Netbios_Name0,
SD.User_Name0,
SD.User_Domain0,
When SD.Obsolete0 = 0 Then 'NO'
Else ' '
When SD.Active0 = 0 Then 'NO'
SD.Client0,
SD.Client_Type0,
SD.Client_Version0,
SD.Hardware_ID0,
SD.Creation_Date0,
SD.SMS_Unique_Identifier0,
SD.Previous_SMS_UUID0,
SD.SMS_UUID_Change_Date0,
AN.AgentName,
DI.AgentSite
From System_DISC SD
Join DiscItemAgents DI On SD.ItemKey = DI.ItemKey
Join Agents AN On DI.AgentID = AN.AgentID
Where SD.Obsolete0 = 1
And SD.Active0 = 0
On the IntelliAdmin Remote Administration For Windows website you can find the following freeware downloads.
IntelliAdmin is the makers of Remote Control LAN Edition and Remote Control Internet Edition remote control solutions. As such many of the freeware applications are designed for remote operation.
Add/Remove program cleaner
http://www.intelliadmin.com/blog/addremovecleaner.exe
“This program allows you to clean up the Add/Remove programs list in the control panel. It should only be used to remove entries that are broken and cannot be removed by running the uninstall program.”
Enable Remote Desktop - Remotely
http://www.intelliadmin.com/RDPRemoteEnabler.exe
“This program allows to enable the remote desktop feature of Windows XP/2000/2003 – Remotely”
Auto Reboot Remover
http://www.intelliadmin.com/blog/AutoRebootSetter.exe
“This program enables or disables the automatic reboot 'feature' of windows XP SP2 after an update has been installed. Saves you from losing important work when you walk away from your computer at the wrong time - and XP decides it is going to close everything without saving.”
Remote Reboot
http://www.intelliadmin.com/blog/RemoteReboot.exe
“Allows you to reboot Windows NT/2000/XP/20003 machines across your LAN. Only shows machines that are on the same domain.”
Floppy Drive Disabler
http://www.intelliadmin.com/FloppyDisabler.exe
“Allows you to easily enable or disable Floppy drives on your Windows 2000, 2003, or XP system”
Floppy Remote Drive Disabler
http://www.intelliadmin.com/FloppyRemoteDisabler.exe
“Allows you to easily enable or disable floppy drives on your Windows 2000, 2003, or XP systems - across your LAN”
CD ROM Drive Disabler
http://www.intelliadmin.com/CDRomDisabler.exe
“Allows you to easily enable or disable CD ROM drives on your Windows 2000, 2003, or XP system”
CD ROM Drive Remote Disabler
http://www.intelliadmin.com/CDRomRemoteDisabler.exe
“Allows you to easily enable or disable CD ROM drives on your Windows 2000, 2003, or XP systems - across your LAN”
USB Drive Disabler
http://www.intelliadmin.com/DisableUSB.exe
“Allows you to easily enable or disable USB drives on your Windows 2000, 2003, or XP system”
USB Remote Drive Disabler
http://www.intelliadmin.com/USBRemoteDisabler.exe
“Allows you to easily enable or disable USB drives on your Windows 2000, 2003, or XP systems - across your LAN”
CNAME Fix
http://www.intelliadmin.com/blog/CNAMEFix.exe
“Fixes a problem in windows 2003, and XP that does not allow computers to share to the machines CNAME. Using a CNAME can be useful for setting up stand-by servers”
Reduced Permissions
http://www.intelliadmin.com/ReducedPermissions.exe
“Allows you to run Internet Explorer in a reduced permissions sandbox. It removes the administrator, and power user groups from IE. - Currently does not work on Windows 2003 due to a MS update”
VNC Flaw Test
http://www.intelliadmin.com/VNCFlawTest.exe
“This program allows you test your installation of VNC for the password bypass vulnerability. It will show you a screenshot of the remote host if you are vulnerable.”
VNC Password Set
http://www.intelliadmin.com/VNCPasswordSet.exe
“This program allows you set the password of your VNC server on your LAN. It also lets you set alternate credentials for connecting to the remote machine. Supports UltraVNC, RealVNC, and TightVNC,”
VNC Navigator
http://www.intelliadmin.com/VNCNavigatorFree.exe
“This program allows you to easily manage your VNC servers. It supports RealVNC, TightVNC, and UltraVNC. Connect to servers with just a double click. It keeps your passwords safe in a 256 Bit encrypted database.”
Additional Links
IntelliAdmin Home Page
http://www.intelliadmin.com/Downloads.htm
Steve Wiseman's blog
http://www.intelliadmin.com/blog/default.htm
The SysObjects table contains one row for each object that has been created in your SQL server database when you install SMS or MOM or if you create a new database yourself.
The Data type for the object types is a 2 character (Char) value and can be executed from any database as mentioned above as well as the systems databases.
By executing the script below you can find what type of object is in your database. You can see which objects are stored procedures, Tables, Views or even system tables.
Name,
'Object Type' = Case
When XType = 'C' Then 'Check Constraint'
When XType = 'D' Then 'Default or Default Constraint'
When XType = 'F' Then 'Foreign Key Constraint'
When XType = 'L' Then 'Log'
When XType = 'FN' Then 'Scalar Function'
When XType = 'IF' Then 'Inlined Table Function'
When XType = 'P' Then 'Stored Procedure'
When XType = 'PK' Then 'Primary Key Constraint'
When XType = 'RF' Then 'Replication Filter Stored Procedure'
When XType = 'S' Then 'System Table'
When XType = 'TF' Then 'Table Function'
When XType = 'TR' Then 'Trigger'
When XType = 'U' Then 'User Table'
When XType = 'UQ' Then 'Unique Constraint'
When XType = 'V' Then 'View'
Else 'Extended Stored Procedure'
End
From SysObjects
Group By Name, XType
I am afraid that I have been indirectly responsible for at least one person crashing (Or rendering useless, much like most division of motor vehicle agents I have encountered) their SMS production database and I do feel bad for them however I cannot take full blame for the incident. I will not go into detail here by just suffice to say that if some people would take the time to read documentation like they read the back covers of play station games at Wal-Mart problems or job reprimand situations can be avoided.
I am not a teacher by any stretch of the word or imagination however I do try and show or explain to people how things work or things that I have learned so that by my mistakes they may learn and avoid the pitfalls that have at times befallen me.
Over the years I have told people to test, test, test, and test again when you are planning on making a change to your production database(s). I have posted articles over the years that detail how you can create a database to play with or develop your scripts and procedures on or destroy and not feel any great loss.
Creating an SMS test database for educational purposes
Posted On: 5/29/2002
http://www.myitforum.com/articles/18/view.asp?id=3016
Copying an SMS database from one server to another
Posted On: 3/18/2002
http://www.myitforum.com/articles/14/view.asp?id=2372
I have also told people to backup their databases using native tools for SQL server or the operating system so that if and when your SMS or MOM database develops an anomaly that cannot be recovered from the database can be restored or placed back into its last functional state.
Backing up your SMS SQL database to a network drive
Posted On: 8/19/2003
http://www.myitforum.com/articles/18/view.asp?id=5915
When disaster strikes
Posted On: 7/17/2003
http://www.myitforum.com/articles/18/view.asp?id=5656
I cannot express more the need to test (On a non production database in a test lab or on the same server if need be) and backup your database to protect your time consuming investment. SMS 2003 is not much different than SMS 2.0 when it comes to backing up your database but it is worth reading the new Microsoft documentation for SMS 2003 for which I have provided the links below.
Scenarios and Procedures for SMS 2003: Maintenance, Backup, and Recovery
http://www.microsoft.com/downloads/details.aspx?FamilyID=d2562e2b-640b-4ab7-ab5a-37995acf2458&Displaylang=en
SMS Technical FAQ: Backup and Recovery
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/tfaq11.mspx
Remember testing and backing up is (not) hard to do and should be done both before and after you make considerable changes to your database so that you can rest assured that your infrastructure will continue to perform as expected.