Have a look at this blog post - http://www.brentozar.com/archive/2013/08/what-queries-are-failing-in-my-sql-server/ - it shows how you can query the extended event data to retrieve the sql_text causing the error.

Hi,

Sorry for the delay in getting back to you - work getting in the way!

It seems that 'validation' is a lot more strict than loading data using XMLBulLoad. I finally...

The error suggests that the XSD does not contain a 'PACKID' element within the PACK element... The example that worked for me looked like this (for the PACK element):-

<xsd:element name="PACK"...

You should be able to load the XML into two tables - as per your original attempt. See attached files.

I've included an XML BulkLoad VB script - if you...

See this documentation on technet...

http://technet.microsoft.com/en-us/library/ms345182(v=sql.100).aspx

Check out the File Watcher task from Konesans (http://www.konesans.com/products/file-watcher-task.aspx).

According to their web-site : "The task will detect changes to existing files as well as new files; both...

Try Professional SQL Server 2000 DTS from Wrox :-http://www.amazon.com/gp/product/0764543687/sr=8-3/qid=1151680753/ref=pd_bbs_3/103-0902090-0047034?ie=UTF8

Also Professional SQL Server 2005 Integration Services (http://www.amazon.com/gp/product/0764584359/qid=1151680901/sr=2-3/ref=pd_bbs_b_2_3/103-0902090-0047034?s=books&v=glance&n=283155)

When I tested "missing mandatory data" earlier, I was using a character field. I've now retried this on a date field and am now generating errors. All I've...

It looks as if the 'validation' that I have previously seen is probably not schema validation as such, but results when supplied data does not conform to the data-types specified...

When you use SQLXMLBulkLoad the XML file will be validated against the schema file, and you can specify an error file that will record any failures including schema problems...

Here's some...

There is a Support Lifecycle page available at Microsoft...

http://support.microsoft.com/default.aspx?pr=lifecycle

Try this script...

selecto2.name as

,

o1.name as [trigger],

case

when OBJECTPROPERTY ( object_id(o1.name ),'ExecIsInsteadOfTrigger') = 1 then 'Instead Of'

when OBJECTPROPERTY ( object_id(o1.name ),'ExecIsAfterTrigger') = 1 then 'After'

end as [Trigger Type],

case OBJECTPROPERTY (...

This is a bug in SP3. See Knowledge Base Article 814113

I've seen this error message when a Package created using SQL 2000 Client Tools is edited using SQL 7.0 Client Tools.