Profiler

I have a trace file that I captured from my production server that I want to replay on my dev box. The database on dev is a restore of the production backup, but the DB_ID of the two is different, which I believe is causing these errors:
No matching connection to execute this on. Will auto-create one.
and
Failed to set proper user name ('empireapi') for the connection
the empireapi username is in the Dev database. I have also dropped and re-created it.
Question:
Is the different databaseid the source of the problem? can I change it somehow? Do you have enough info to determine?
Thanks,
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
Yes. Yes. And Yes.
In books online there is a topic:
Replaying Traces
in the Administering SQL Server section. You can find the
requirements for replay traces listed there. Included is
that the database ids need to be the same.
To correct this, you can restore the master database from
the production server to the dev box.
The other work around would be to remove database ids from
the trace. Then set all the users captured in the trace to
have a default database of the target database. The commands
will then be executed in the default database so the
database id isn't an issue.
-Sue
On Thu, 10 Jun 2004 11:16:31 -0500, "Kevin3NF"
<KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote:

>I have a trace file that I captured from my production server that I want to replay on my dev box. The database on dev is a restore of the production backup, but the DB_ID of the two is different, which I believe is causing these errors:
>No matching connection to execute this on. Will auto-create one.
>and
>Failed to set proper user name ('empireapi') for the connection
>the empireapi username is in the Dev database. I have also dropped and re-created it.
>Question:
>Is the different databaseid the source of the problem? can I change it somehow? Do you have enough info to determine?
>Thanks,
|||Thanks Sue...I will get to one of your two excellent suggestions right away.
Fortunately, the DEV box is completely under my control for at least another
week, then it becomes a production box, so I can do anything I need to with
it :-)
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:d87ic0tqi2vj8g4vti340ukfa80corr6dj@.4ax.com... [vbcol=seagreen]
> Yes. Yes. And Yes.
> In books online there is a topic:
> Replaying Traces
> in the Administering SQL Server section. You can find the
> requirements for replay traces listed there. Included is
> that the database ids need to be the same.
> To correct this, you can restore the master database from
> the production server to the dev box.
> The other work around would be to remove database ids from
> the trace. Then set all the users captured in the trace to
> have a default database of the target database. The commands
> will then be executed in the default database so the
> database id isn't an issue.
> -Sue
> On Thu, 10 Jun 2004 11:16:31 -0500, "Kevin3NF"
> <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote:
to replay on my dev box. The database on dev is a restore of the production
backup, but the DB_ID of the two is different, which I believe is causing
these errors:[vbcol=seagreen]
re-created it.[vbcol=seagreen]
somehow? Do you have enough info to determine?
>