Call Logging System Call Logging Application Architecture?
Call logging application architecture? - call logging system
as an internal system to detect design calls for the use of SQL Server 2003 requires the entity-relationship diagram
|
Subscribe to:
Post Comments (Atom)
4 comments:
A table is usually sufficient. In general, it depends on your application.
ExeptionLog range of areas:
ID: integer
Machine Name: Name of the network of the machine on which the exception occurred
UserID: UserID identifies the user who encountered the problem
ExceptionDate: Date of Emergency
Exception: Name type of emergency
Message: Exception message
Stack trace: stack trace when the exception.
In addition, if a web application or may include the following information to your table.
QueryStringData: list of variable names and values of query string
FormData: List names of all the form variables and values
The question is very vague. Develop an application form requires a thorough knowledge of the application is in use, and data which are interested in saving for future use.
Thank you.
A table is usually sufficient. In general, it depends on your application.
ExeptionLog range of areas:
ID: integer
Machine Name: Name of the network of the machine on which the exception occurred
UserID: UserID identifies the user who encountered the problem
ExceptionDate: Date of Emergency
Exception: Name type of emergency
Message: Exception message
Stack trace: stack trace when the exception.
In addition, if a web application or may include the following information to your table.
QueryStringData: list of variable names and values of query string
FormData: List names of all the form variables and values
The question is very vague. Develop an application form requires a thorough knowledge of the application is in use, and data which are interested in saving for future use.
Thank you.
A table is usually sufficient. In general, it depends on your application.
ExeptionLog range of areas:
ID: integer
Machine Name: Name of the network of the machine on which the exception occurred
UserID: UserID identifies the user who encountered the problem
ExceptionDate: Date of Emergency
Exception: Name type of emergency
Message: Exception message
Stack trace: stack trace when the exception.
In addition, if a web application or may include the following information to your table.
QueryStringData: list of variable names and values of query string
FormData: List names of all the form variables and values
The question is very vague. Develop an application form requires a thorough knowledge of the application is in use, and data which are interested in saving for future use.
Thank you.
A table is usually sufficient. In general, it depends on your application.
ExeptionLog range of areas:
ID: integer
Machine Name: Name of the network of the machine on which the exception occurred
UserID: UserID identifies the user who encountered the problem
ExceptionDate: Date of Emergency
Exception: Name type of emergency
Message: Exception message
Stack trace: stack trace when the exception.
In addition, if a web application or may include the following information to your table.
QueryStringData: list of variable names and values of query string
FormData: List names of all the form variables and values
The question is very vague. Develop an application form requires a thorough knowledge of the application is in use, and data which are interested in saving for future use.
Thank you.
Post a Comment