You've got this answer in template don't you? <g> I did some more research
via dejanews and found multiple instances of the "610" error with your
reply. I did try and check the support link and searched for "610/925",
"610", "925", "Error 610", "msg 610"....etc. Only came up with two articles
that didn't seem to address this issue at all. This seems to be a somewhat
common occurence, I was suprised to not find anything in the support db.
Maybe it was how I queried it, but I would think I'd of been able to find
Is this fixed in 7.0? We did manage to work around it by breaking up the
query (it should've been shot and put out of it's misery).
Would you really want a repro script for this? You'd need the data as well
as the tables, right? That's a whole lotta data...
>> Subject: Help: Msg 610 Maximum number of databases exceeded?
>Q. Why do I get an error "#610 - Maximum number of databases that may be
>accessed by a transaction is <x>. This number has been exceeded by this
>query." when running a SQL Server query?
>A. There is also a very similar error 925.
>Assuming the query doesn't really access more than <x> databases then this
>SQL bug caused by a complex query that has confused the SQL
>Look for any known reasons for this bug at http://support.microsoft.com -
>search on 610/925 and SQL and kbbug. If your problem does not match any of
>these and you have already applied the latest service pack then either post
>reproduction script for an MVP to report for you or call the problem in to
> Neil Pike MVP/MCSE. Protech Computing Ltd
> (Please post ALL replies to the newsgroup only unless indicated otherwise)
> For SQL FAQ entries see
> http://go.compuserve.com/sqlserver (library 1) - latest stuff is always