the query below may help you;

SELECT Trc.EventID, Trc.ColumnID, Evt.name as Event_Description, Col.name as Column_Description

FROM ::fn_trace_geteventinfo(1) Trc

JOIN sys.trace_events Evt ON Trc.eventID = Evt.trace_event_id...

Refer the link below for the events on the Default trace.

http://blogs.technet.com/b/vipulshah/archive/2007/04/16/default-trace-in-sql-server-2005.aspx

Yes, you can have MAXDOP...

VIEW ANY DATABASE permission is a new, server-level permission. A login that is granted with this permission can see metadata that describes all databases, regardless of whether the login...

Refer the link for the Max. no of Processor supported on SQL Server

Maximum Number of Processors Supported by the Editions of SQL Server

MAXDOP - Maximum Degree of Parallism

Sets the maximum number of processors the query processor can use to execute a statement.

Fewer processors may be used depending on the current system...

In general SQL Server Maintenance Plan covers what is basic to maintain databases.

When the requirement goes beyond the basic, automating using scripts may help.

Also when there are more SQL...

1. Check if distribution database exist though the Replication is dropped

2. If so drop the distribution database

3. To drop the distribution database by over - restoring of some user database

4....

Thanks it's worked after changing the database default file location on properties !!

Refer the MS artilce on

"

The SQL Server service cannot start when you change a startup parameter for a clustered instance of SQL Server 2000 or of SQL Server 2005 to...

Torn I/O is often referred to as a torn page in SQL Server documentation. A torn I/O occurs when a partial write takes place, leaving the data in an invalid...

If you are accessing the Setup files from remote server mapped on a network drive, ensure it available.

I am facing the error below

SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=8476. Thread=1028. Client. Instance=PROD_SQL1. VD=Global\VDI_FB7A53C0-02D2-4469-A676-6868465A1904_0_SQLVDIMemoryName_0.

It occurs on using Quest LiteSpeed 5.0.1

SQL Server 2000 Enterprise Edition 32 Bit

Windows 2003 Enterprise...

Failure Sending Mail: the transport failed to connect the server

Error related to Mail Server. Ensure the Mail server given is correct and it is up & running.

Also check if there...

I also faced similar issue, wherein SQL Server 2000 ERRORLOG grown up to 300 MB.

Sp_cycle_errorlog / DBCC ERRORLOG failed to recreate new errorlog file.

Solution: Bounce the SQL Server Services.