When we create a db,the create command will create a data
file with an Extension .mdf,as well as a transaction log
file with extension .ldf
Any additional or secondary data files have .ndf extension
For reading the log files (.ldf) an undocumented system
stored procedure sp_readerrorlog is there. This SP allows
you to read the contents of the SQL Server error log files
directly from a query window and also allows you to search
for certain keywords when reading the error file. This is
not new to SQL Server 2005, but this tip discusses how this
works for SQL Server 2005.
This is a sample of the stored procedure for SQL Server
2005. You will see that when this gets called it calls an
extended stored procedure xp_readerrorlog.
This procedure takes four parameters:
Value of error log file you want to read: 0 = current, 1 =
Archive #1, 2 = Archive #2, etc...
Log file type: 1 or NULL = error log, 2 = SQL Agent log
Search string 1: String one you want to search for
Search string 2: String two you want to search for to
further refine the results
If you do not pass any parameters this will return the
contents of the current error log.
Example 1
EXEC sp_readerrorlog 6
This statement returns all of the rows from the 6th
archived error log.
Example 2
EXEC sp_readerrorlog 6, 1, '2005'
This returns just 8 rows wherever the value 2005 appears.
Example 3
EXEC sp_readerrorlog 6, 1, '2005', 'exec'
This returns only rows where the value '2005' and 'exec'
exist.
Even though sp_readerrolog accepts only 4 parameters, the
extended stored procedure accepts at least 7 parameters.
If this extended stored procedure is called directly the
parameters are as follows:
Value of error log file you want to read: 0 = current, 1 =
Archive #1, 2 = Archive #2, etc...
Log file type: 1 or NULL = error log, 2 = SQL Agent log
Search string 1: String one you want to search for
Search string 2: String two you want to search for to
further refine the results
?
?
Sort order for results: N'asc' = ascending, N'desc' =
descending
If you are working on a SQL database and if suddenly a
developer changes the code and your queries results start
giving errors,how will you check using a T-SQL query (on
system tables) that what has changed in the database.
There is a trigger defined for INSERT operations on a
table, in an OLTP system. The trigger is written to
instantiate a COM object and pass the newly insterted rows
to it for some custom processing. What do you think of this
implementation? Can this be implemented better?
How to find the second largest salary in the emp database and
also How to find 3rd,4th and so on ........ in the emp database
plz mail the answer @ mak2786@gmail.com
if we have a column (Key) in a table.
and values of that column is
Key
1
1
1
2
2
3
3
4
4
5
5
5
and we want to show the data after query..like..
1(3)
2(3)
3(2)
4(2)
5(3)
how many times a single term comes..