Active Issues

NOTE: THIS REPORT HAS NOT BEEN ACCESSED BY MICROSOFT.

Tags Severity
SQL Configurations High
SQL Configurations High
Database Indexes High
Database Indexes High
Database Files High
Database Indexes High
Database Files High
Database Files High
Database Options High
SQL Server maintenance High
Event Log Analysis High
Event Log Analysis High
Set;Storage;Checklist High
Ready;RolesAndFeatures;Checklist High
Set;DisasterRecovery;Checklist High
Set;Configuration;Checklist High
Move;Data;Checklist High
SQL Server maintenance High
OS Configurations for SQL High
SQL Performance High
SQL Security High
SQL Security High
Upgrade Readiness High
Upgrade Readiness High
Disaster Recovery High
Update Management High
Update Management High
Operational Excellence High
Set;Security;Checklist Medium
Set;Network;Checklist Medium
Set;Hardware;Checklist Medium
Ready;RolesAndFeatures;Checklist Medium
Checklist;RolesAndFeatures;Ready Medium
Set;Network;Checklist Medium
Ready;Scenario;Checklist Medium
Cluster Resource Medium
SQL Configurations Medium
SQL Configurations Medium
SQL Configurations Medium
Database Files Medium
Database Files Medium
Database Indexes Medium
Database Files Medium
Database Indexes Medium
Database Indexes Medium
Database Indexes Medium
Database Indexes Medium
Database Indexes Medium
Database Files Medium
Database Options Medium
Database Options Medium
Database Options Medium
SQL Error Log Medium
SQL Error Log Medium
SQL Error Log Medium
Event Log Analysis Medium
Set;Configuration;Checklist Medium
Set;Storage;Checklist Medium
Set;DisasterRecovery;Checklist Medium
Set;Hardware;Checklist Medium
Set;Configuration;Checklist Medium
Set;Network;Checklist Medium
Database Files Medium
SQL Performance Medium
SQL Security Medium
SQL Security Medium
SQL Security Medium
SQL Security Medium
SQL Security Medium
SQL Server Info Medium
Upgrade Readiness Medium
Upgrade Readiness Medium
Upgrade Readiness Medium
Disaster Recovery Medium
Operational Security Medium
Operational Excellence Medium
Update Management Medium
Move;Monitor;Checklist Low
Set;Configuration;Checklist Low
Set;Storage;Checklist Low
SQL Configurations Low
Database Options Low
SQL Server maintenance Low
Set;Network;Checklist Low
Move;Provision;Checklist Low
Operational Excellence Low
OS Configurations for SQL Low
OS Configurations for SQL Low
SQL Security Low
SQL Security Low
Operational Excellence Low
Monitoring Low
Environmental Dependencies Low
SQL Configurations Informational
SQL Configurations Informational
Issue Name Affected Targets
The SQL Server Configuration setting, xp_cm MOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
The Value configured for SQL Server Confi MOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
There are foreign keys with no supporting MARGE.INVESTIGACIONES.CL\I2;Telefonos_Cautin; M
Indexes have been identified with an indexMARGE.INVESTIGACIONES.CL\I2;ReportServer$I2; M
Too many virtual log files may impact SQL MARGE.INVESTIGACIONES.CL\I2;i2_REPOME_2011
Databases identified with one or more tableMARGE.INVESTIGACIONES.CL\I2;JENAINPOL__LOG; MAR
SQL Server instance has only one tempdb da MOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
Databases have been identified with one o MOU.INVESTIGACIONES.CL;SharePoint_Config:File: Sh
Database(s) identified with recovery modelMOU.INVESTIGACIONES.CL; SUSDB; MOU.INVESTIGAC
User Databases found with Full or Bulk log MOU.INVESTIGACIONES.CL;Agenda_Net; MOU.INVESTIG
System Event Log: Microsoft-Windows-FailoLIZA.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.C
The System Event log contains Event 1548.LIZA.INVESTIGACIONES.CL; MAGGIE.INVESTIGACIONES.
Move any user or system database files from MARGE.INVESTIGACIONES.CL
Windows Failover Clustering Instances are nMOU.INVESTIGACIONES.CL
Implement HADR solutions for SQL Server dMOU.INVESTIGACIONES.CL;Agenda_Net; MOU.INVESTI
SQL Server instance can be configured to uMOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
Review your requirements and select the eMOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
DBCC CHECKDB has not been run within sevMOU.INVESTIGACIONES.CL;Agenda_Net; MOU.INVESTI
The Windows 2008/R2 and later OS power M s AGGIE.INVESTIGACIONES.CL; LIZA.INVESTIGACIONES
Paging file usage is high MARGE.INVESTIGACIONES.CL
Databases identified with Guest user enablMARGE.INVESTIGACIONES.CL\I2;Base_de_Datos_Cautin
SQL Server service is running under the Lo MARGE.INVESTIGACIONES.CL\SP_FOUNDATION; MARGE
Deprecated database SET options found MOU:Agenda_Net; MOU:ALMA; MOU:JENAINTEL; MOU:OR
The current version of SQL Server does notMOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
Disaster recovery plan is not documented
Establish a comprehensive, proactive secur
No procedures and tools in place for check
Statistics are not regularly updated.
Local accounts with administrative rights LIZA.INVESTIGACIONES.CL; MAGGIE.INVESTIGACIONES
Multiple network adapters are not supportLIZA.INVESTIGACIONES.CL; MAGGIE.INVESTIGACIONES
Microsoft Azure virtual machines can have LIZA.INVESTIGACIONES.CL; MAGGIE.INVESTIGACIONES
Reconfigure existing failover clusters LIZA.INVESTIGACIONES.CL; MAGGIE.INVESTIGACIONES
Some Windows roles are not supported in LIZA.INVESTIGACIONES.CL; MAGGIE.INVESTIGACIONES
Static IP address are not allowed in Azure LIZA.INVESTIGACIONES.CL; MAGGIE.INVESTIGACIONES
Only virtualized instances are allowed in A LIZA.INVESTIGACIONES.CL; MAGGIE.INVESTIGACIONES
The SQL Server Agent resource policy is setSQL
to Server Agent
The SQL Server configuration setting, clr e MARGE.INVESTIGACIONES.CL\I2
The SQL Server configuration setting, Ad H MOU.INVESTIGACIONES.CL
The SQL Server configuration setting, showMOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
Data and Transaction Log files are not on s MOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
One or more user database files are place MOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
Tables and indexed views have been identifMARGE.INVESTIGACIONES.CL\I2;Telefonos_Cautin; M
Databases identified with auto-growth set MOU.INVESTIGACIONES.CL;Agenda_Net;File: Agenda_N
Fragmented indexes were found MARGE.INVESTIGACIONES.CL\I2; Cautin_; MOU.INVES
Tables have been identified that have mor MOU.INVESTIGACIONES.CL;Tfs_SISTEMAS; MOU.INVESTI
Tables and/or indexed views have been iden MARGE.INVESTIGACIONES.CL\I2;Telefonos_Cautin_Lo
Tables have been identified that do not havMARGE.INVESTIGACIONES.CL\I2;Telefonos_Cautin; M
Tables have been identified that do not ha MARGE.INVESTIGACIONES.CL\I2;Telefonos_Cautin_L
TempDB initial database Size may be too smMOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
User Databases found that have collations MOU.INVESTIGACIONES.CL:ALMA; MOU.INVESTIGACION
Database(s) identified with AUTO_CREATE_MOU.INVESTIGACIONES.CL;SharePoint_AdminContent
Database(s) identified with AUTO_UPDATE_MOU.INVESTIGACIONES.CL;SharePoint_AdminContent
SQL Error Log: 17806: SSPI handshake failedMOU.INVESTIGACIONES.CL
SQL Error Log: 3041: BACKUP failed to co MOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES
The current SQL Server error log is too larg MARGE.INVESTIGACIONES.CL\I2
System Event Log: EventLog:6008: The pre MAGGIE.INVESTIGACIONES.CL
Compress database tables and indexes to rMOU.INVESTIGACIONES.CL;Agenda_Net; MOU.INVESTI
Consider moving the databases out of sys MARGE.INVESTIGACIONES.CL\SP_FOUNDATION;master;
Optimize your backup strategy with MicrosMOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
Choose the best virtual machine size for y MAGGIE.INVESTIGACIONES.CL; LIZA.INVESTIGACIONES
Configure tempdb to scale allocation cont MOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
Configure SQL Server to accept incoming c MARGE.INVESTIGACIONES.CL\SP_FOUNDATION; MARGE
Transaction log size is larger than database MOU.INVESTIGACIONES.CL;Agenda_Net; MOU.INVESTI
High number of Context Switches/sec MARGE.INVESTIGACIONES.CL
SQL Server logins identified that do not a MOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
“Allow log on locally” user right may have LIZA.INVESTIGACIONES.CL; MAGGIE.INVESTIGACIONES
“Allow log on through Remote Desktop” use LIZA.INVESTIGACIONES.CL; MAGGIE.INVESTIGACIONES
Non-Default logins are provisioned to SQL SMOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
The SQL Server Agent service is not using MARGE.INVESTIGACIONES.CL\SP_FOUNDATION; MARGE
The latest service pack or hotfix for SQL SerMOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
One or more databases are using EnterpriseMOU.INVESTIGACIONES.CL;Tfs_aba; MOU.INVESTIGACIO
Server network protocol, Named Pipes, ha MOU.INVESTIGACIONES.CL
Large backup or restore history tables ma MARGE.INVESTIGACIONES.CL\I2
DBCC checks are not regularly scheduled.
SQL Server infrastructure changes do not g
Index defragmentation is not regularly sch
SQL Server updates are applied too infrequ
Expect to restart for host updates - It’s be LIZA.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.C
Registry entry RealtimeIsUniversal must beLIZA.INVESTIGACIONES.CL; MAGGIE.INVESTIGACIONES
Make sure you don’t currently use restricted MARGE.INVESTIGACIONES.CL
The SQL Server configuration setting, max sMOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
User database is set to compatibility level l MOU.INVESTIGACIONES.CL:SUSDB; MARGE.INVESTIGACIO
Databases identified that have not had a fuMOU.INVESTIGACIONES.CL;SharePoint_AdminContent
Implement Windows Authentication in Micro MARGE.INVESTIGACIONES.CL\SP_FOUNDATION
Review the currently available Microsoft AzMOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
Avoid creating user objects in the master MOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
Data, Log or Tempdb partitions are not form MOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
Page file set to “Automatically manage paging
LIZA.INVESTIGACIONES.CL; MAGGIE.INVESTIGACIONES
Non-Default users are provisioned to db_o MOU.INVESTIGACIONES.CL:Agenda_Net; MOU.INVESTI
Ownership issues in SQL Server Agent jobs MOU.INVESTIGACIONES.CL\Respaldo instancia MOU_Resp
Microsoft SQL Server staff roles are not clea
Performance baselines are not captured.
Hardware that is needed for disaster recover
The SQL Server configuration setting, defa MOU.INVESTIGACIONES.CL; MARGE.INVESTIGACIONES.
The SQL Server configuration setting, SQL MARGE.INVESTIGACIONES.CL\I2
Status Created On Notes
Failed 8/3/2015 7:01:56 PM ""
Failed 8/3/2015 7:02:01 PM ""
Failed 8/3/2015 7:02:30 PM ""
Failed 8/3/2015 7:02:37 PM ""
Failed 8/3/2015 7:03:01 PM ""
Failed 8/3/2015 7:03:03 PM ""
Failed 8/3/2015 7:03:07 PM ""
Failed 8/3/2015 7:03:11 PM ""
Failed 8/3/2015 7:03:23 PM ""
Failed 8/3/2015 7:03:25 PM ""
Failed 8/3/2015 7:04:56 PM ""
Failed 8/3/2015 7:05:18 PM ""
Failed 8/3/2015 7:07:33 PM ""
Failed 8/3/2015 7:07:38 PM ""
Failed 8/3/2015 7:07:39 PM ""
Failed 8/3/2015 7:07:46 PM ""
Failed 8/3/2015 7:07:50 PM ""
Failed 8/3/2015 7:07:52 PM ""
Failed 8/3/2015 7:08:03 PM ""
Failed 8/3/2015 7:08:30 PM ""
Failed 8/3/2015 7:09:01 PM ""
Failed 8/3/2015 7:09:18 PM ""
Failed 8/3/2015 7:09:37 PM ""
Failed 8/3/2015 7:09:45 PM ""
Failed 8/3/2015 7:10:00 PM ""
Failed 8/3/2015 7:10:50 PM ""
Failed 8/3/2015 7:10:54 PM ""
Failed 8/3/2015 7:11:06 PM ""
Failed 8/3/2015 7:01:19 PM ""
Failed 8/3/2015 7:01:20 PM ""
Failed 8/3/2015 7:01:22 PM ""
Failed 8/3/2015 7:01:23 PM ""
Failed 8/3/2015 7:01:25 PM ""
Failed 8/3/2015 7:01:26 PM ""
Failed 8/3/2015 7:01:29 PM ""
Failed 8/3/2015 7:01:38 PM ""
Failed 8/3/2015 7:01:51 PM ""
Failed 8/3/2015 7:01:56 PM ""
Failed 8/3/2015 7:01:58 PM ""
Failed 8/3/2015 7:02:02 PM ""
Failed 8/3/2015 7:02:05 PM ""
Failed 8/3/2015 7:02:12 PM ""
Failed 8/3/2015 7:02:20 PM ""
Failed 8/3/2015 7:02:34 PM ""
Failed 8/3/2015 7:02:40 PM ""
Failed 8/3/2015 7:03:02 PM ""
Failed 8/3/2015 7:03:04 PM ""
Failed 8/3/2015 7:03:04 PM ""
Failed 8/3/2015 7:03:07 PM ""
Failed 8/3/2015 7:03:12 PM ""
Failed 8/3/2015 7:03:16 PM ""
Failed 8/3/2015 7:03:18 PM ""
Failed 8/3/2015 7:03:39 PM ""
Failed 8/3/2015 7:03:50 PM ""
Failed 8/3/2015 7:04:30 PM ""
Failed 8/3/2015 7:06:07 PM ""
Failed 8/3/2015 7:07:31 PM ""
Failed 8/3/2015 7:07:32 PM ""
Failed 8/3/2015 7:07:38 PM ""
Failed 8/3/2015 7:07:42 PM ""
Failed 8/3/2015 7:07:47 PM ""
Failed 8/3/2015 7:07:48 PM ""
Failed 8/3/2015 7:07:54 PM ""
Failed 8/3/2015 7:08:25 PM ""
Failed 8/3/2015 7:09:01 PM ""
Failed 8/3/2015 7:09:04 PM ""
Failed 8/3/2015 7:09:05 PM ""
Failed 8/3/2015 7:09:08 PM ""
Failed 8/3/2015 7:09:12 PM ""
Failed 8/3/2015 7:09:24 PM ""
Failed 8/3/2015 7:09:29 PM ""
Failed 8/3/2015 7:09:46 PM ""
Failed 8/3/2015 7:09:51 PM ""
Failed 8/3/2015 7:10:13 PM ""
Failed 8/3/2015 7:10:14 PM ""
Failed 8/3/2015 7:10:19 PM ""
Failed 8/3/2015 7:10:53 PM ""
Failed 8/3/2015 7:01:18 PM ""
Failed 8/3/2015 7:01:21 PM ""
Failed 8/3/2015 7:01:21 PM ""
Failed 8/3/2015 7:01:48 PM ""
Failed 8/3/2015 7:03:13 PM ""
Failed 8/3/2015 7:03:27 PM ""
Failed 8/3/2015 7:07:45 PM ""
Failed 8/3/2015 7:07:47 PM ""
Failed 8/3/2015 7:07:55 PM ""
Failed 8/3/2015 7:07:57 PM ""
Failed 8/3/2015 7:08:08 PM ""
Failed 8/3/2015 7:09:09 PM ""
Failed 8/3/2015 7:09:10 PM ""
Failed 8/3/2015 7:10:55 PM ""
Failed 8/3/2015 7:10:56 PM ""
Failed 8/3/2015 7:10:57 PM ""
Failed 8/3/2015 7:01:46 PM ""
Failed 8/3/2015 7:01:54 PM ""
Resolved Issues
NOTE: THIS REPORT HAS NOT BEEN ACCESSED BY MICROSOFT.
Category Severity
Issue Name Resolved Date
Notes
Not Applicable Issues
NOTE: THIS REPORT HAS NOT BEEN ACCESSED BY MICROSOFT.
Tags Severity
Issue Name Affected Targets
Status Created On Notes