Sounds about right...

The only problem with that solution is that sysdepends is not reliable.  I can garantee that you miss a few refferences with your current code.

The alternative is to...

No, if you want to change 'em along with the database name you need to run a separate command.

Check out "ALTER DATABASE" in the books online.

modify filename section.

Undo the work the DTA did.. should give you a break.

Then in query analyser, replay the trace for all the query and show the execution plans.

From there tune all the...

exec sp_renamedb 'oldname', 'newname'

... unless you can tell us what you are trying to do... maybe there's an alternative slution to your problem!!

Short of going to your workplace I see nothing else I can do.

Good luck finding the solution to that problem .

Can you undo the work the DTA made, and upgrade the indexes using only the slowest running queries?

There are no difference in the select statement part.  Only the tools to display the data changed.  I wanted to make sure that the query returned the correct results!

Can you...

Try this :

select text from dbo.syscomments where id in (select id from sysdepends where depid = object_id('OneTableNameHere')) and id not in(select constid from sysconstraints where id =object_id('OneTableNameHere'))

Just supply one...

What results are you getting if you run the same queries from Query analyser?

This works fine for me :

Sub a()

    Dim sql As String

    Dim rs5 As ADODB.Recordset

    Set rs5 = New ADODB.Recordset

            sql = "select" & _

                " text" & _

               ...

IS it possible that the text is in th elistbox, but not visisble to you?

Also do you have obejcts that containt more than 4000 characters (they will be saved in...

Look at the query results in QA.  The go is NOT SAVED in the table.  You'll have to put one manullay if you need it.

Let me put it in simple words.  I keep the production databases safe from even myself... and I'm the only programmer/DBA in the building.  That's because I already screwed up...

Or an even simpler solution (maybe it even saves a few cpu cycles)...

declare @d TABLE (BirthDate datetime)

INSERT INTO @d (BirthDate)

SELECT '1955-10-25'

UNION

SELECT '1960-11-25'

UNION

SELECT '1965-11-05'

UNION

SELECT '1970-10-15'

UNION

SELECT '1970-12-20'

UNION

SELECT '1970-11-01'

UNION

SELECT '1970-10-31'

UNION

SELECT '1970-11-30'

SELECT BirthDate, DATEADD(YY,...