better method for DTS: event

Showing posts with label event. Show all posts

Friday, March 9, 2012

Is there any way to know any user Connect / Disconnect from the SQL Server?

Hi All,
Is there any way to know any user Connect / Disconnect from the SQL Server?
Such as: In any kind of "Method" OR "Event Log"
Thanks !
Please do not crosspost.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"SOHO" <hkwin2000@.hotmail.com> schrieb im Newsbeitrag
news:u2Grt$lcFHA.3184@.TK2MSFTNGP15.phx.gbl...
> Hi All,
> Is there any way to know any user Connect / Disconnect from the SQL
> Server?
> Such as: In any kind of "Method" OR "Event Log"
>
> --
> Thanks !
>
>
|||You can switch on the logging for valid / invalid /all logons for the
registry. Its located under the properties of the Server in the EM, Tab
Security.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"SOHO" <hkwin2000@.hotmail.com> schrieb im Newsbeitrag
news:u2Grt$lcFHA.3184@.TK2MSFTNGP15.phx.gbl...
> Hi All,
> Is there any way to know any user Connect / Disconnect from the SQL
> Server?
> Such as: In any kind of "Method" OR "Event Log"
>
> --
> Thanks !
>
>
|||sorry!
Thanks !
"Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> glsD:OoNXjDmcFHA.2288@.TK2MSFTNGP14.phx.g bl...
> Please do not crosspost.
> --
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "SOHO" <hkwin2000@.hotmail.com> schrieb im Newsbeitrag
> news:u2Grt$lcFHA.3184@.TK2MSFTNGP15.phx.gbl...
>
|||Thanks for your reply!
Thanks !
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com>
??:%23STaOPmcFHA.2736@.TK2MSFTNGP12.phx.gbl...
> From SQL Enterprise manager you can enable logging for all logins (both
> failed & successful) in the Server Properties dialog box (Security tab,
> Security group box, Audit level radio button group). This will cause
> SQL Server to write messages to the SQL errorlog every time a user
> connects to the SQL server (whether it's a successful or failed login
> attempt). But that won't tell you anything about logouts (i.e.
> disconnects).
> Probably the best way to monitor this stuff is with SQL Profiler. You
> can enable the 'Security Audit|Audit Login', 'Security Audit|Audit Login
> Failed' & 'Security Audit|Audit Logout' events. You can get profiler to
> write its trace data to a file or a SQL table so that you can query
> against that data at a later time.
> That would be about as close to an "event log" containing both logout &
> login information that you can get your hands on. There's no way,
> without altering the SQL Server binaries, to hook into the login/logout
> event of a SQL server.
> BTW, you ought to try to restrict your post to one or, at most, two
> newsgroups.
> --
> *mike hodgson* |/ database administrator/ | mallesons stephen jaques
> *T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
> *E* mailto:mike.hodgson@.mallesons.nospam.com |* W*
> http://www.mallesons.com
>
> SOHO wrote:
>
|||SQL Server Profiler does not work for you?
Or use sp_who stored procedure.
"SOHO" <hkwin2000@.hotmail.com> wrote in message
news:u2Grt$lcFHA.3184@.TK2MSFTNGP15.phx.gbl...
> Hi All,
> Is there any way to know any user Connect / Disconnect from the SQL
> Server?
> Such as: In any kind of "Method" OR "Event Log"
>
> --
> Thanks !
>
>

Is there any way to know any user Connect / Disconnect from the SQL Server?

Hi All,
Is there any way to know any user Connect / Disconnect from the SQL Server?
Such as: In any kind of "Method" OR "Event Log"
--
Thanks !Please do not crosspost.
--
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"SOHO" <hkwin2000@.hotmail.com> schrieb im Newsbeitrag
news:u2Grt$lcFHA.3184@.TK2MSFTNGP15.phx.gbl...
> Hi All,
> Is there any way to know any user Connect / Disconnect from the SQL
> Server?
> Such as: In any kind of "Method" OR "Event Log"
>
> --
> Thanks !
>
>|||You can switch on the logging for valid / invalid /all logons for the
registry. Its located under the properties of the Server in the EM, Tab
Security.
--
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"SOHO" <hkwin2000@.hotmail.com> schrieb im Newsbeitrag
news:u2Grt$lcFHA.3184@.TK2MSFTNGP15.phx.gbl...
> Hi All,
> Is there any way to know any user Connect / Disconnect from the SQL
> Server?
> Such as: In any kind of "Method" OR "Event Log"
>
> --
> Thanks !
>
>|||sorry!
--
Thanks !
"Jens Süßmeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> ¼¶¼g©ó¶l¥ó·s»D:OoNXjDmcFHA.2288@.TK2MSFTNGP14.phx.gbl...
> Please do not crosspost.
> --
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "SOHO" <hkwin2000@.hotmail.com> schrieb im Newsbeitrag
> news:u2Grt$lcFHA.3184@.TK2MSFTNGP15.phx.gbl...
>> Hi All,
>> Is there any way to know any user Connect / Disconnect from the SQL
>> Server?
>> Such as: In any kind of "Method" OR "Event Log"
>>
>> --
>> Thanks !
>>
>|||This is a multi-part message in MIME format.
--070603060003080705000406
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
From SQL Enterprise manager you can enable logging for all logins (both
failed & successful) in the Server Properties dialog box (Security tab,
Security group box, Audit level radio button group). This will cause
SQL Server to write messages to the SQL errorlog every time a user
connects to the SQL server (whether it's a successful or failed login
attempt). But that won't tell you anything about logouts (i.e.
disconnects).
Probably the best way to monitor this stuff is with SQL Profiler. You
can enable the 'Security Audit|Audit Login', 'Security Audit|Audit Login
Failed' & 'Security Audit|Audit Logout' events. You can get profiler to
write its trace data to a file or a SQL table so that you can query
against that data at a later time.
That would be about as close to an "event log" containing both logout &
login information that you can get your hands on. There's no way,
without altering the SQL Server binaries, to hook into the login/logout
event of a SQL server.
BTW, you ought to try to restrict your post to one or, at most, two
newsgroups.
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
SOHO wrote:
>Hi All,
>Is there any way to know any user Connect / Disconnect from the SQL Server?
>Such as: In any kind of "Method" OR "Event Log"
>
>
--070603060003080705000406
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>From SQL Enterprise manager you can enable logging for all logins
(both failed & successful) in the Server Properties dialog box
(Security tab, Security group box, Audit level radio button group).
This will cause SQL Server to write messages to the SQL errorlog every
time a user connects to the SQL server (whether it's a successful or
failed login attempt). But that won't tell you anything about logouts
(i.e. disconnects). 
 
Probably the best way to monitor this stuff is with SQL Profiler. You
can enable the 'Security Audit|Audit Login', '</tt><tt>Security Audit|</tt><tt>Audit
Login Failed' & '</tt><tt>Security Audit|</tt><tt>Audit Logout'
events. You can get profiler to write its trace data to a file or a
SQL table so that you can query against that data at a later time. 
 
That would be about as close to an "event log" containing both logout
& login information that you can get your hands on. There's no
way, without altering the SQL Server binaries, to hook into the
login/logout event of a SQL server. 
 
BTW, you ought to try to restrict your post to one or, at most, two
newsgroups. 
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
-- 
 mike
hodgson | database administrator
| mallesons stephen jaques 
T +61 (2) 9296 3668 | F +61
(2) 9296 3885 | M +61
(408) 675 907 
E
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> | W <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a> 
</div>
 
 
SOHO wrote:
<blockquote cite="midu2Grt$lcFHA.3184@.TK2MSFTNGP15.phx.gbl" type="cite">
<pre wrap="">Hi All,
Is there any way to know any user Connect / Disconnect from the SQL Server?
Such as: In any kind of "Method" OR "Event Log"
</pre>
</blockquote>
</body>
</html>
--070603060003080705000406--|||Thanks for your reply!
--
Thanks !
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com>
'?:%23STaOPmcFHA.2736@.TK2MSFTNGP12.phx.gbl...
> From SQL Enterprise manager you can enable logging for all logins (both
> failed & successful) in the Server Properties dialog box (Security tab,
> Security group box, Audit level radio button group). This will cause
> SQL Server to write messages to the SQL errorlog every time a user
> connects to the SQL server (whether it's a successful or failed login
> attempt). But that won't tell you anything about logouts (i.e.
> disconnects).
> Probably the best way to monitor this stuff is with SQL Profiler. You
> can enable the 'Security Audit|Audit Login', 'Security Audit|Audit Login
> Failed' & 'Security Audit|Audit Logout' events. You can get profiler to
> write its trace data to a file or a SQL table so that you can query
> against that data at a later time.
> That would be about as close to an "event log" containing both logout &
> login information that you can get your hands on. There's no way,
> without altering the SQL Server binaries, to hook into the login/logout
> event of a SQL server.
> BTW, you ought to try to restrict your post to one or, at most, two
> newsgroups.
> --
> *mike hodgson* |/ database administrator/ | mallesons stephen jaques
> *T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
> *E* mailto:mike.hodgson@.mallesons.nospam.com |* W*
> http://www.mallesons.com
>
> SOHO wrote:
>>Hi All,
>>Is there any way to know any user Connect / Disconnect from the SQL
>>Server?
>>Such as: In any kind of "Method" OR "Event Log"
>>
>>
>|||Use profiler to monitor user connection is too expensive.
"SOHO" wrote:
> Thanks for your reply!
> --
> Thanks !
>
> "Mike Hodgson" <mike.hodgson@.mallesons.nospam.com>
> '?:%23STaOPmcFHA.2736@.TK2MSFTNGP12.phx.gbl...
> > From SQL Enterprise manager you can enable logging for all logins (both
> > failed & successful) in the Server Properties dialog box (Security tab,
> > Security group box, Audit level radio button group). This will cause
> > SQL Server to write messages to the SQL errorlog every time a user
> > connects to the SQL server (whether it's a successful or failed login
> > attempt). But that won't tell you anything about logouts (i.e.
> > disconnects).
> >
> > Probably the best way to monitor this stuff is with SQL Profiler. You
> > can enable the 'Security Audit|Audit Login', 'Security Audit|Audit Login
> > Failed' & 'Security Audit|Audit Logout' events. You can get profiler to
> > write its trace data to a file or a SQL table so that you can query
> > against that data at a later time.
> >
> > That would be about as close to an "event log" containing both logout &
> > login information that you can get your hands on. There's no way,
> > without altering the SQL Server binaries, to hook into the login/logout
> > event of a SQL server.
> >
> > BTW, you ought to try to restrict your post to one or, at most, two
> > newsgroups.
> >
> > --
> > *mike hodgson* |/ database administrator/ | mallesons stephen jaques
> > *T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
> > *E* mailto:mike.hodgson@.mallesons.nospam.com |* W*
> > http://www.mallesons.com
> >
> >
> >
> > SOHO wrote:
> >
> >>Hi All,
> >>
> >>Is there any way to know any user Connect / Disconnect from the SQL
> >>Server?
> >>Such as: In any kind of "Method" OR "Event Log"
> >>
> >>
> >>
> >>
> >
>
>|||SQL Server Profiler does not work for you?
Or use sp_who stored procedure.
"SOHO" <hkwin2000@.hotmail.com> wrote in message
news:u2Grt$lcFHA.3184@.TK2MSFTNGP15.phx.gbl...
> Hi All,
> Is there any way to know any user Connect / Disconnect from the SQL
> Server?
> Such as: In any kind of "Method" OR "Event Log"
>
> --
> Thanks !
>
>

Is there any way to know any user Connect / Disconnect from the SQL Server?

Hi All,
Is there any way to know any user Connect / Disconnect from the SQL Server?
Such as: In any kind of "Method" OR "Event Log"
Thanks !Please do not crosspost.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"SOHO" <hkwin2000@.hotmail.com> schrieb im Newsbeitrag
news:u2Grt$lcFHA.3184@.TK2MSFTNGP15.phx.gbl...
> Hi All,
> Is there any way to know any user Connect / Disconnect from the SQL
> Server?
> Such as: In any kind of "Method" OR "Event Log"
>
> --
> Thanks !
>
>|||You can switch on the logging for valid / invalid /all logons for the
registry. Its located under the properties of the Server in the EM, Tab
Security.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"SOHO" <hkwin2000@.hotmail.com> schrieb im Newsbeitrag
news:u2Grt$lcFHA.3184@.TK2MSFTNGP15.phx.gbl...
> Hi All,
> Is there any way to know any user Connect / Disconnect from the SQL
> Server?
> Such as: In any kind of "Method" OR "Event Log"
>
> --
> Thanks !
>
>|||sorry!
Thanks !
"Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> glsD:OoNXjDmcFH
A.2288@.TK2MSFTNGP14.phx.gbl...
> Please do not crosspost.
> --
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "SOHO" <hkwin2000@.hotmail.com> schrieb im Newsbeitrag
> news:u2Grt$lcFHA.3184@.TK2MSFTNGP15.phx.gbl...
>|||Thanks for your reply!
--
Thanks !
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com>
'?:%23STaOPmcFHA.2736@.TK2MSFTNGP12.phx.gbl...
> From SQL Enterprise manager you can enable logging for all logins (both
> failed & successful) in the Server Properties dialog box (Security tab,
> Security group box, Audit level radio button group). This will cause
> SQL Server to write messages to the SQL errorlog every time a user
> connects to the SQL server (whether it's a successful or failed login
> attempt). But that won't tell you anything about logouts (i.e.
> disconnects).
> Probably the best way to monitor this stuff is with SQL Profiler. You
> can enable the 'Security Audit|Audit Login', 'Security Audit|Audit Login
> Failed' & 'Security Audit|Audit Logout' events. You can get profiler to
> write its trace data to a file or a SQL table so that you can query
> against that data at a later time.
> That would be about as close to an "event log" containing both logout &
> login information that you can get your hands on. There's no way,
> without altering the SQL Server binaries, to hook into the login/logout
> event of a SQL server.
> BTW, you ought to try to restrict your post to one or, at most, two
> newsgroups.
> --
> *mike hodgson* |/ database administrator/ | mallesons stephen jaques
> *T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
> *E* mailto:mike.hodgson@.mallesons.nospam.com |* W*
> http://www.mallesons.com
>
> SOHO wrote:
>
>|||SQL Server Profiler does not work for you?
Or use sp_who stored procedure.
"SOHO" <hkwin2000@.hotmail.com> wrote in message
news:u2Grt$lcFHA.3184@.TK2MSFTNGP15.phx.gbl...
> Hi All,
> Is there any way to know any user Connect / Disconnect from the SQL
> Server?
> Such as: In any kind of "Method" OR "Event Log"
>
> --
> Thanks !
>
>

Wednesday, March 7, 2012

Is there any way to have an email sent on an event

I'm using SQL with an Access form for the front end. Is there anyway to have an email sent on the trigger of an event within the form? I'm not sure where to even begin.

A good place to start is Books Online. Look up Triggers, SQL Agent, Jobs.

The path you are headed down has a short but steep learning curve.

|||

Unless you are using SQL Server 2005, you should not use the trigger approach to send email directly. This is due to the fact that triggers behave synchronously letting your transaction wait for the response of the external mail sending application / procedure. This could stale your transaction process and let other users wait for ressources to transaction might block. SQL Server uses SQL Server Service broker for sending mails with the DBMail, putting the mail in a queue, sending the mail asynchronously. For SQL Server 2000 you would have to implement your custom solution, writing an entry in a table with the appropiate mail information and grabbing the information from the table periodically to send the emails via an agent job.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Friday, February 24, 2012

Is there any reason to use port 1433?

Hello
I am new to SQL security.
Some days ago I happened to open my event log and found lots of attacks have
been going on to my SQL server 2005. Maybe for some months. I have been
using firewall and Windows integrated authentication. The attacks might be
not quite successful. Anyway, I changed the SQL server port from 1433 to
something another. Strikingly all the attacks have gone. Now I am curious
why they use port number 1433. Is there any reason to use the port, benefit
or something? Or is there any danger or caution to use something other than
1433?Han
By default sql server uses tcp/ip 1433 port for communication. so it is
quite common to get attack on that port.
VT
"Han" <hp4444@.kornet.net.korea> wrote in message
news:O3yHPmyKHHA.1280@.TK2MSFTNGP04.phx.gbl...
> Hello
> I am new to SQL security.
> Some days ago I happened to open my event log and found lots of attacks
> have been going on to my SQL server 2005. Maybe for some months. I have
> been using firewall and Windows integrated authentication. The attacks
> might be not quite successful. Anyway, I changed the SQL server port from
> 1433 to something another. Strikingly all the attacks have gone. Now I am
> curious why they use port number 1433. Is there any reason to use the
> port, benefit or something? Or is there any danger or caution to use
> something other than 1433?
>|||Thank you for your quick reply, vt.
Yes, 1433 is one of well-known ports. So, what I am asking is, why you
should use the well-known port.
To now one problem I found giving up the 1433 is adding my own port number
to my connection strings.
server=server-name,10001; ...
That's just trivial pain compared with the freedom from lots of ridiculous
attacks. I hope the pain is all I should consider, but I am not sure...
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:uCgwesyKHHA.4992@.TK2MSFTNGP04.phx.gbl...
> Han
> By default sql server uses tcp/ip 1433 port for communication. so it is
> quite common to get attack on that port.
>
> VT
>
>
> "Han" <hp4444@.kornet.net.korea> wrote in message
> news:O3yHPmyKHHA.1280@.TK2MSFTNGP04.phx.gbl...
>|||Han
Well you don't need to take all those hazels of passing port number, you can
configure sql server to use which ever port you want
To do that, if you are using sql 2000
Open sql server network utility under Microsoft SQL Server program group.
Select property of TCP/IP and change the port number there..
thats it , sql srever will start listining to that port
VT
"Han" <hp4444@.kornet.net.korea> wrote in message
news:%23QvONA0KHHA.1424@.TK2MSFTNGP04.phx.gbl...
> Thank you for your quick reply, vt.
> Yes, 1433 is one of well-known ports. So, what I am asking is, why you
> should use the well-known port.
> To now one problem I found giving up the 1433 is adding my own port number
> to my connection strings.
> server=server-name,10001; ...
> That's just trivial pain compared with the freedom from lots of ridiculous
> attacks. I hope the pain is all I should consider, but I am not sure...
> "vt" <vinu.t.1976@.gmail.com> wrote in message
> news:uCgwesyKHHA.4992@.TK2MSFTNGP04.phx.gbl...
>|||Han,
1433 is the default port that SQL Server uses for TCP/IP client
communication. You can configure that to be another port, but hackers
will find them and attempt hacking there too.
I wrote a utility to do a bit of self defense for these hacking attempts.
http://www.creeksolutions.com/Produ...92/Default.aspx
BlockSSHacking runs as a Windows service protecting your SQL Server from
brute force hacking attempts coming from the Internet.
The service checks your system every 5 minutes (configurable setting)
for evidence of ongoing hacking. If such attempts are in progress then
those source addresses are blocked from future access to your server
(quickly leading to you recovering your bandwidth).
BlockSSHacking notifies you via email when it has blocked someone from
hacking your system.
Henrik
Han wrote:
> Hello
> I am new to SQL security.
> Some days ago I happened to open my event log and found lots of attacks ha
ve
> been going on to my SQL server 2005. Maybe for some months. I have been
> using firewall and Windows integrated authentication. The attacks might be
> not quite successful. Anyway, I changed the SQL server port from 1433 to
> something another. Strikingly all the attacks have gone. Now I am curious
> why they use port number 1433. Is there any reason to use the port, benefi
t
> or something? Or is there any danger or caution to use something other tha
n
> 1433?
>

Friday, March 9, 2012

Is there any way to know any user Connect / Disconnect from the SQL Server?

Is there any way to know any user Connect / Disconnect from the SQL Server?

Is there any way to know any user Connect / Disconnect from the SQL Server?

Is there any way to know any user Connect / Disconnect from the SQL Server?

Is there any way to know any user Connect / Disconnect from the SQL Server?

Wednesday, March 7, 2012

Is there any way to have an email sent on an event

Friday, February 24, 2012

Is there any reason to use port 1433?

better method for DTS

Blog Archive

About Me