RE: Traces for Upgrade Advisor Tool SQL Server 2005?

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
.

Relevant Pages

  • Re: One Web Service updates SQL, another cant?
    ... section of the Trace Properties dialog. ... And then I start getting the database closed errors on subsequent calls. ... > The error suggests that somehow the connection to SQL Server is being ... Could we have a look at your connection string? ...
    (microsoft.public.sqlserver.security)
  • RE: cannot delete a record in sql server 2005 through asp program
    ... Using trace script he provided and trace file created by the script. ... SQL Server database by the asp application. ... Microsoft Online Community Support ... a Microsoft Support Engineer within 2 business day is acceptable. ...
    (microsoft.public.sqlserver.programming)
  • Re: Profiler Security
    ... There's no way to restrict what a user of trace can see - if they ... etc. coming into SQL Server. ... >> want to assign the developers the sys admin sql role. ...
    (microsoft.public.sqlserver.security)
  • Re: Auditing sql server at runtime
    ... SQL Server native tools don't do any port sniffing. ... Use SQL Profiler to define your trace, ... Create a SQL Agent job to run that trace, paste the script into it. ...
    (microsoft.public.sqlserver.clients)
  • Re: Auditing sql server at runtime
    ... "Manpreet Singh" wrote in message ... DB Dev SQL Server 2005 ... Use SQL Profiler to define your trace, ... Create a SQL Agent job to run that trace, ...
    (microsoft.public.sqlserver.clients)