----------oct 210 a 2020 2019

31oct2019 alta se reporto

* falta reportar cifras baja 2019

* falta reportar cifra baja 2020
--------------------------------
microservicios con contenedores y mensajerias
https://www.youtube.com/watch?v=QdwxZsDrQWo
microsoft/app-innovation-team

bitdefender Soporte123$
------------------------

https://www.youtube.com/watch?v=eedEQl76vWY debate
azitromicina 100 gr 5 dias
flumicil 600mg 1 cada 8h
prednisoma 20 mg 1 cada 8h
aspirina 100 gr 1 diaria
analgan 12 h

levocetirizina 5 mg marcela sinositis

cloruro de sodio 1000 ml

3 ampolla de cemin 30 gotas
1 ampolla complejo b vitamina
-------------------------------------

268.94 evelin

MSDTC
NT AUTHORITY\NetworkService

https://www.sqlshack.com/es/las-herramientas-de-monitorizacion-de-sql-server-para-
el-rendimiento-de-la-memoria/

Admin zimbra
Admin_1234*/.

40514 2946

1390091474001 ruc coac santa ana

44588547 ISAC LLAGUAL

TICKET 44547244 16/07/2020

44532692 CNT --

--------------------------
exec sp_configure 'show advanced options', 1;
GO
RECONFIGURE;
GO
sp_configure 'Database Mail XPs', 1;
GO
RECONFIGURE
GO

IF EXISTS (
SELECT 1 FROM sys.configurations
WHERE NAME = 'Database Mail XPs' AND VALUE = 0)
BEGIN
PRINT 'Enabling Database Mail XPs'
EXEC sp_configure 'show advanced options', 1;
RECONFIGURE
EXEC sp_configure 'Database Mail XPs', 1;
RECONFIGURE
END

--------------
telnet 172.100.1.122 4040

netstat -an |findstr 4040

Test-NetConnection 172.100.1.122 -Port 4040

rout print 124 coonect

netsh advfirewall firewall add rule name="Puerto TCP 443" dir=in action=allow
protocol=TCP localport=443

--------------------
equysum
190.63.156.129
190.63.134.89
200.25.197.8
200.25.207.114
--------------------
telconet
200.93.207.190/30
200.93.207.189
186.5.11.4
186.5.56.4
---------------------

190.63.134.190:8085

=============
portoviejo
-------------
172.100.7.9
255.255.255.0
172.100.7.245
186.5.11.4
186.5.56.4
-------------

tcpdump -n -i interface icmp and "dst 190.63.156.129" or "dst 200.93.207.189"

pEDRO045 financial
Pemb1140/*05 correo
Pemb1155

------------
Is database mail enabled
In SQL Server Management Studio, connect to an instance of SQL Server by using a
query editor window, and then execute the following code:

SQL

Copy
sp_configure 'show advanced', 1;
GO
RECONFIGURE;
GO
sp_configure;
GO
In the results pane, confirm that the run_value for Database Mail XPs is set to 1.
If the run_value is not 1, Database Mail is not enabled. Database Mail is not
automatically enabled to reduce the number of features available for attack by a
malicious user. For more information, see Understanding Surface Area Configuration.

If you decide that it is appropriate to enable Database Mail, execute the following
code:

SQL

Copy
sp_configure 'Database Mail XPs', 1;
GO
RECONFIGURE;
GO
To restore the sp_configure procedure to its default state, which does not show
advanced options, execute the following code:

SQL

Copy
sp_configure 'show advanced', 0;
GO
RECONFIGURE;
GO
Are users properly configured to send mail
To send Database Mail, users must be a member of the DatabaseMailUserRole database
role in the msdb database. Members of the sysadmin fixed server role and
msdbdb_owner role are automatically members of the DatabaseMailUserRole role. To
list all other members of the DatabaseMailUserRole execute the following statement:

SQL

Copy
EXEC msdb.sys.sp_helprolemember 'DatabaseMailUserRole';
To add users to the DatabaseMailUserRole role, use the following statement:

SQL

Copy
USE msdb;
GO

sp_addrolemember @rolename = 'DatabaseMailUserRole'

,@membername = '<database user>';
To send Database Mail, users must have access to at least one Database Mail
profile. To list the users (principals) and the profiles to which they have access,
execute the following statement.

SQL

Copy
EXEC msdb.dbo.sysmail_help_principalprofile_sp;
Use the Database Mail Configuration Wizard to create profiles and grant access to
profiles to users.

Is database mail started

The Database Mail External Program is activated when there are e-mail messages to
be processed. When there have been no messages to send for the specified time-out
period, the program exits. To confirm the Database Mail activation is started,
execute the following statement:

SQL

Copy
EXEC msdb.dbo.sysmail_help_status_sp;
If the Database Mail activation is not started, execute the following statement to
start it:

SQL

Copy
EXEC msdb.dbo.sysmail_start_sp;
If the Database Mail external program is started, check the status of the mail
queue with the following statement:

SQL

Copy
EXEC msdb.dbo.sysmail_help_queue_sp @queue_type = 'mail';
The mail queue should have the state of RECEIVES_OCCURRING. The status queue may
vary from moment to moment. If the mail queue state is not RECEIVES_OCCURRING, try
restarting the queue. Stop the queue using the following statement:

SQL

Copy
EXEC msdb.dbo.sysmail_stop_sp;
Then start the queue using the following statement:

SQL

Copy
EXEC msdb.dbo.sysmail_start_sp;
Note

Use the length column in the result set of sysmail_help_queue_sp to determine the
number of e-mails in the Mail queue.

Do problems affect some or all accounts

If you have determined that some but not all profiles can send mail, then you may
have problems with the Database Mail accounts used by the problem profiles. To
determine which accounts are successful in sending mail, execute the following
statement:

SQL

Copy
SELECT sent_account_id, sent_date FROM msdb.dbo.sysmail_sentitems;
If a non-working profile does not use any of the accounts listed, then it is
possible that all the accounts available to the profile are not working properly.
To test individual accounts, use the Database Mail Configuration Wizard to create a
new profile with a single account, and then use the Send Test E-Mail dialog box to
send mail using the new account.

To view the error messages returned by Database Mail, execute the following
statement:

SQL

Copy
SELECT * FROM msdb.dbo.sysmail_event_log;