Showing posts with label failed. Show all posts
Showing posts with label failed. Show all posts

Friday, February 24, 2012

Capture Records That Failed Insertion From XML

Does anyone know an effective way to capture any records that failed to
insert into a table when inserting from an xml document in SQL Svr
2000?

thanks.

-akAyron (akitchen@.lrs.com) writes:
> Does anyone know an effective way to capture any records that failed to
> insert into a table when inserting from an xml document in SQL Svr
> 2000?

It would certainly help if you told us how you insert your records.
Openxml or XML bulk load?

Particularly in the matter case, I would recommend trying
microsoft.public.sqlserver.xml.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thanks for the reply, Erland. I'm new to the XML bulk insert. I'll look
into that method. I've also transitioned the topic to the group that
you mentioned.

-ak|||"Ayron" <akitchen@.lrs.com> wrote in message
news:1108507580.773174.268630@.l41g2000cwc.googlegr oups.com...
> Does anyone know an effective way to capture any records that failed to
> insert into a table when inserting from an xml document in SQL Svr
> 2000?

I have used sqxmlbulkload.
Not really investigated it in depth but the default behaviour is to crash
and burn if a record contains invalid data.
I wrote an access app which a support user investigates problems with.
They import the xml file to a table and a screen iterates through all fields
comparing values with the datatypes.
It marks records as bad.
The screen shows only bad records and uses conditional highlighting to
highlight the bad field in a record.

--
Regards,
Andy O'Neill

Sunday, February 19, 2012

Capture IP Address

Does anyone know how to configure profiler or a way to capture an IP address
of a Failed Login Attempt user to a SQL Server 2000?
Thanks in advance.
JohnJohn,
If you are getting hack in attempts, just go to the command prompt and
type
netstat -n
The SQL attacks will be on 1433 and will be listed as time wait (assuming
you check when you are being hacked).
Russ Stevens|||Keeping up to date with database security can get so stressful makes me sick
to gut.
Thank you very much Russ for your helpful post. I really appreciate it.
-J
"Russell Stevens" <rustyprogrammer@.online.nospam> wrote in message
news:u3mohmk7FHA.3976@.TK2MSFTNGP15.phx.gbl...
> John,
> If you are getting hack in attempts, just go to the command prompt and
> type
> netstat -n
> The SQL attacks will be on 1433 and will be listed as time wait (assuming
> you check when you are being hacked).
> Russ Stevens
>|||Hmmm...I apologize if this is a novice observation but I just noticed
something interesting that I thought I would share...
I have some MS Access front end databases linked to SQL Server 2000
databases as the backend (tables) on our internal network. I create new SQL
logins for every user that requests access to the database and capture every
user action through SQL Profiler. In analyzing the Profiler trace logs I
noticed some Login Failed attempts to our Master database which really
raised my concern. The interesting part is that the Login Failed attempt
kept saying user 'Admin'. I know that we don't have a specific user name to
any of our databases named 'Admin' especially to our Master. I just did a
test and went to open my linked table through MS Access to SQL Server 2000
and that the Profiler logged the event as a Login Failed attempt to the
Master database even though the linked table is to one of my other defined
databases. Then the dsn odbc login pop up comes up and then I log in with
my valid specified user name and password which is not 'Admin' and am able
to login successfully. All of the Login Failed attempts with 'Admin'
throughout my trace logs have a successful login immediately after with a
valid user name. So it appears that when accessing a SQL Server table
through a link from MS Access it by default tries to access the Master
database with the default user name of 'Admin' and then prompts the user for
the valid login name and password. So maybe these weren't hack attempts
(which I am truly hoping)?
Would be interested if someone could confirm to me if this whole process is
accurate?
Thanks in advance.
-J
"John" <IDontLikeSpam@.Nowhere.com> wrote in message
news:%23pr5wns7FHA.3808@.TK2MSFTNGP10.phx.gbl...
> Keeping up to date with database security can get so stressful makes me
> sick to gut.
> Thank you very much Russ for your helpful post. I really appreciate it.
> -J
> "Russell Stevens" <rustyprogrammer@.online.nospam> wrote in message
> news:u3mohmk7FHA.3976@.TK2MSFTNGP15.phx.gbl...
>