The fundamental problem with writing an error to a log within a transaction that is subsequently rolled back is that everything written by the connection within the transaction is rolled...

You can log the error to the SQL Server system log by specifying "WITH LOG" on your call to RAISERROR. These log entries survive the transaction rollback:

BEGIN TRAN

BEGIN TRY

...

Sorry you are having problems. I just re-tested by downloading the unmodified Geocode.sql from the resources link at the end of the article and executed:

EXEC spGeocode '1234 N. Main...

Thanks for the suggestion about a table variable. I know that operations on table variables don't get rolled back. Maybe I can find a way to make use...

Another great article, Jeff. Thanks! I had no idea that an inline table-valued function could be so much faster than an scalar UDF.

I confirmed the "times two" results...

The link to the original script is under "Resources" at the bottom of the article (http://www.sqlservercentral.com/articles/geocode/70061)

The direct link is: http://www.sqlservercentral.com/Files/Geocode.sql/6085.sql

Thanks! sp_Tables_Ex is just what I was looking for.

Normally attributes that are parsed by SQLDOM are stored in the table #tblDOMAttributes (which can be joined to table #tblDOM via the DEID column).

In HTML 4, "selected" is really supposed...

Jon,

Sure, you could parse HTML that is already stored in a column.

I wrote a brief post[/url] on this sort of thing at http://sf.net/p/sqldom/discussion/general/thread/5bf1fdb6/

In a nutshell, the #spactDOMLoad procedure...

I did stress test, and spent some time optimizing.

I don't have detailed benchmarks handy, but by way of example parsing the Google home page (once the HTML is loaded in...

{message deleted}

Thanks, Jeff.

I thought my standard pattern of simple joins would do about as well:

SELECT DISTINCT p.CustomerID

FROM

#Purchase p

JOIN #Purchase p2 ON

p.CustomerID = p2.CustomerID...

We have SQL servers hosted with two different providers that we are happy with:

SoftLayer

Database Mart

Both of these have been very reliable in production for 3 years or so. SoftLayer...

>>>Cursors I truly believe can be avoided altogether.

An example of when a cursor is necessary: when interacting with a SQL-based API that encapsulates business logic (Microsoft Dynamics GP for...

Indexed views provide the most value when you are indexing on columns from multiple tables that are joined in the view--particularly if all of the columns you need to access...