"FELIX" wrote:

> Hi:
>
> We are working with Upgrade Advisor Tool  (for the migration SQL Server 2000
> to SQL Server 2005) and we had seen that this tool recomended the use of
> tracesfiles.
>
> What´s usefull to trace?
>
> --
> FELIX

> Hi Felix,
>
> http://msdn2.microsoft.com/en-us/library/ms144256.aspx pertains to the
> Upgrade Advisor Tool and might answer some of your questions.
>
> Additionally, the following books online information is related to your
> question involving traces:
>
> In SQL Server 2005, global trace flags set by a session take effect in other
> sessions immediately. Also, some trace flags from SQL Server 2000 do not
> exist in SQL Server 2005.
>
> Component
> Database Engine
>
> Description
> We recommend that you disable all trace flags before you upgrade to SQL
> Server 2005. You can enable the trace flags after you verify that the trace
> flags are required and are still valid in SQL Server 2005. If you must
> reenable trace flags in SQL Server 2005, you should perform additional tests
> on your instance of SQL Server.
>
> SQL Server 2005 introduces global and session level trace flags. In SQL
> Server 2005, trace flags can be specified as either local or global by using
> an additional argument (-1) in the DBCC TRACEON command. If this argument is
> not specified, the default value is local. This behavior is different from
> SQL Server 2000 in which the trace flags are always set globally.
>
> Also, in SQL Server 2000, a trace flag set in session A does not
> automatically take effect in an already existing session B. Instead, this
> trace flag takes effect only after the first time any trace flag is set in
> session B. This behavior is nondeterministic in SQL Server 2000 and is
> deterministic in SQL Server 2005. In SQL Server 2005, global trace flags set
> in session A are set immediately in other concurrent sessions.
>
> Finally, if you are using replication in your implementation, trace flag
> 1400 is not enabled by default with SQL Server 2005.  Someone from the
> database mirroring group might be able to provide specifics as to the
> reasoning for this change.
>
> Regards,
>
> Keith Wilson
> Microsoft SQL Server
>
> ==================================================
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "FELIX" wrote:
>
> > Hi:
> >
> > We are working with Upgrade Advisor Tool  (for the migration SQL Server 2000
> > to SQL Server 2005) and we had seen that this tool recomended the use of
> > tracesfiles.
> >
> > What´s usefull to trace?
> >
> > --
> > FELIX

"FELIX" wrote:

> Hi Keith:
>
> Thank you very much for your answer though it isn’t exactly that we are
> asking.
>
> Because of the tool  UPGRADE ADVISOR SQL SERVER 2005 needs to have trace
> files to help in the migration of SQL SERVER 2000 to SQL SERVER 2005; our
> question is: What events, columns,  and so on you recommend us to trace?
>
> Best Regards
>
> --
> FELIX
>
>
> "Keith.Wilson@NoSpam.microsoft.com" escribió:
>
> > Hi Felix,
> >
> > http://msdn2.microsoft.com/en-us/library/ms144256.aspx pertains to the
> > Upgrade Advisor Tool and might answer some of your questions.
> >
> > Additionally, the following books online information is related to your
> > question involving traces:
> >
> > In SQL Server 2005, global trace flags set by a session take effect in other
> > sessions immediately. Also, some trace flags from SQL Server 2000 do not
> > exist in SQL Server 2005.
> >
> > Component
> > Database Engine
> >
> > Description
> > We recommend that you disable all trace flags before you upgrade to SQL
> > Server 2005. You can enable the trace flags after you verify that the trace
> > flags are required and are still valid in SQL Server 2005. If you must
> > reenable trace flags in SQL Server 2005, you should perform additional tests
> > on your instance of SQL Server.
> >
> > SQL Server 2005 introduces global and session level trace flags. In SQL
> > Server 2005, trace flags can be specified as either local or global by using
> > an additional argument (-1) in the DBCC TRACEON command. If this argument is
> > not specified, the default value is local. This behavior is different from
> > SQL Server 2000 in which the trace flags are always set globally.
> >
> > Also, in SQL Server 2000, a trace flag set in session A does not
> > automatically take effect in an already existing session B. Instead, this
> > trace flag takes effect only after the first time any trace flag is set in
> > session B. This behavior is nondeterministic in SQL Server 2000 and is
> > deterministic in SQL Server 2005. In SQL Server 2005, global trace flags set
> > in session A are set immediately in other concurrent sessions.
> >
> > Finally, if you are using replication in your implementation, trace flag
> > 1400 is not enabled by default with SQL Server 2005.  Someone from the
> > database mirroring group might be able to provide specifics as to the
> > reasoning for this change.
> >
> > Regards,
> >
> > Keith Wilson
> > Microsoft SQL Server
> >
> > ==================================================
> >
> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> >
> > ==================================================
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> > "FELIX" wrote:
> >
> > > Hi:
> > >
> > > We are working with Upgrade Advisor Tool  (for the migration SQL Server 2000
> > > to SQL Server 2005) and we had seen that this tool recomended the use of
> > > tracesfiles.
> > >
> > > What´s usefull to trace?
> > >
> > > --
> > > FELIX

"Keith.Wilson@NoSpam.microsoft.com" wrote:

> Hi Felix,
>
> Could you please provide more details as to the type of configuration you
> will be upgrading from SQL Server 2000 to SQL Server 2005?  For example, the
> operating system, SQL SKU, number of processor(s), type of processor(s), and
> current SQL implementation (e.g. cluster or not, replicated or not ...) would
> be helpful in addressing your question.
>
> Regards,
> 
> Keith Wilson
> Microsoft SQL Server
>
> ==================================================
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> 
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "FELIX" wrote:
>
> > Hi Keith:
> >
> > Thank you very much for your answer though it isn’t exactly that we are
> > asking.
> >
> > Because of the tool  UPGRADE ADVISOR SQL SERVER 2005 needs to have trace
> > files to help in the migration of SQL SERVER 2000 to SQL SERVER 2005; our
> > question is: What events, columns,  and so on you recommend us to trace?
> >
> > Best Regards
> >
> > --
> > FELIX
> >
> >
> > "Keith.Wilson@NoSpam.microsoft.com" escribió:
> >
> > > Hi Felix,
> > >
> > > http://msdn2.microsoft.com/en-us/library/ms144256.aspx pertains to the
> > > Upgrade Advisor Tool and might answer some of your questions.
> > >
> > > Additionally, the following books online information is related to your
> > > question involving traces:
> > >
> > > In SQL Server 2005, global trace flags set by a session take effect in other
> > > sessions immediately. Also, some trace flags from SQL Server 2000 do not
> > > exist in SQL Server 2005.
> > >
> > > Component
> > > Database Engine
> > >
> > > Description
> > > We recommend that you disable all trace flags before you upgrade to SQL
> > > Server 2005. You can enable the trace flags after you verify that the trace
> > > flags are required and are still valid in SQL Server 2005. If you must
> > > reenable trace flags in SQL Server 2005, you should perform additional tests
> > > on your instance of SQL Server.
> > >
> > > SQL Server 2005 introduces global and session level trace flags. In SQL
> > > Server 2005, trace flags can be specified as either local or global by using
> > > an additional argument (-1) in the DBCC TRACEON command. If this argument is
> > > not specified, the default value is local. This behavior is different from
> > > SQL Server 2000 in which the trace flags are always set globally.
> > >
> > > Also, in SQL Server 2000, a trace flag set in session A does not
> > > automatically take effect in an already existing session B. Instead, this
> > > trace flag takes effect only after the first time any trace flag is set in
> > > session B. This behavior is nondeterministic in SQL Server 2000 and is
> > > deterministic in SQL Server 2005. In SQL Server 2005, global trace flags set
> > > in session A are set immediately in other concurrent sessions.
> > >
> > > Finally, if you are using replication in your implementation, trace flag
> > > 1400 is not enabled by default with SQL Server 2005.  Someone from the
> > > database mirroring group might be able to provide specifics as to the
> > > reasoning for this change.
> > >
> > > Regards,
> > >
> > > Keith Wilson
> > > Microsoft SQL Server
> > >
> > > ==================================================
> > >
> > > When responding to posts, please "Reply to Group" via your newsreader so
> > > that others may learn and benefit from your issue.
> > >
> > > ==================================================
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > >
> > >
> > > "FELIX" wrote:
> > >
> > > > Hi:
> > > >
> > > > We are working with Upgrade Advisor Tool  (for the migration SQL Server 2000
> > > > to SQL Server 2005) and we had seen that this tool recomended the use of
> > > > tracesfiles.
> > > >
> > > > What´s usefull to trace?
> > > >
> > > > --
> > > > FELIX