Hi, we are facing problem with the sql queries given below query number one gives the output as workstation and total logon failure attempts from that workstation which is fine 1) select logonsvr,workstnid, count (username) from winadlogon where evtid="681" group by workstnid order by workstnid;
query number 2 is generating list username-workstnid-hits from the user e.g. userA-workstation A- 3 userB-Workstation A -2 userc-workstation B -1 2)select time,workstnid,username count (username) from winadlogon where evtid="681" group by username order by workstnid; as shown in above example we are getting the list. If user A also has attempted login from workstation B the it is not displayed as we have done grouping by username. we need output such as userA-workstation A -3 userA-workstation B -2 if user is attempling log on from various workstations the this query should show all entries for the user for all workstations from where it has tried log on and hits from each workstation logon and while group by username is in place. please suggest if there is any solution to this problem. Thanks, Narasimha -----Original Message----- From: Gleb Paharenko [mailto:[EMAIL PROTECTED] Sent: Monday, March 14, 2005 3:00 PM To: mysql@lists.mysql.com Subject: Re: Wrong bytesec nightmare! Hello. You may use --extend-check option with myisamchk, but usually it finds a lot of garbage, and should be used as a last resort. Francisco Lopez <[EMAIL PROTECTED]> wrote: > Hello all, > I am getting quite desperate on this, since I've been trying to recover > my diary of a whole year of travelling which was stored in a MyISAM > table for a couples of weeks now! The MySQL server was running in a XP > machine and suddenly the hard disk crashed starting my particular > nightmare. I had to use recovery tools to scan the disk and I thought I > was saved when I found the *.frm, *.MYI and *.MYD files and was able to > recover them, but when I tried get the tables back into MySQL and > backup their contents, I found a series of errors that have kept me > down ever since! > The first complain I got when I selected the table was: > > Didn't find any fields in table 'news' > > I then checked the table for errors, and got: > > mysql> check table news; > +----------+-------+-------- -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
