Have into the database in system database data dictionary, know the meaning of each field in each table, how to quickly understand the specific definition of each stored procedure, specific purpose!! And then according to the stored procedure development program

CodePudding user response:

This can't quick, you only have to read the source code, run it before, this would be a long boring process,
If your program is simple, it is better to write a stored procedure may be more quick,

CodePudding user response:

reference 1st floor lich2005 response:

this can't quick, you only have to read the source code, run it before, this would be a long boring process,
If your program is simple, it is better to write a stored procedure may be more quick,

Is that there is no source

CodePudding user response:

Open interface, tracking its SQL statements, contributes to an understanding of the system,

CodePudding user response:

Bother to tell how to trace

CodePudding user response:

SQL=="tool" SQL Server Profiler=& gt; Event select="check the show all columns=" column filter="HostName class begins with XX