To rebuild the master database in SQL Server 2000 (Rebuild Master utility)

To rebuild the master database        

1. Shutdown Microsoft® SQL Server™ 2000, and then run Rebuildm.exe. This is located in the Program Files\Microsoft SQL Server\80\Tools\Binn directory.
2. In the Rebuild Master dialog box, click Browse.
3. In the Browse for Folder dialog box, select the \Data folder on the SQL Server 2000 compact disc or in the shared network directory from which SQL Server 2000 was installed, and then click OK.
4. Click Settings. In the Collation Settings dialog box, verify or change settings used for the master database and all other databases.

IF YOUR MSDB DATABASE HAS BEEN MARKED SUSPECT AND YOU ARE UNABLE TO TAKE BACK UP FROM MAINTENANCE PLAN THEN FOLLOW THIS PROCEDURE

This is for sql 2000

1.. In SQL Server Enterprise Manager, right-click the server name and

click Properties.
2.. On the General tab, click Startup Parameters.
3.. Add a new parameter as "-T3608" (without the quotation marks).
After you add trace flag 3608, follow these steps:
1.. Stop, and then restart SQL Server.
2.. Make sure that the SQL Server Agent service is not currently running.
3.. Detach the msdb database as follows: or use the query msdb detach query.

Select Edit All Records In SQL Server 2008

In SQL Server 2008, the default numbers of rows for selecting and editing records are 1000 and 200 respectively. Sometimes if the records are greater than 200 and you want to edit some record then you have to change the query to get all the records. This is time consuming and you have to repeat this exercise whenever the records are greater than 200. The solution for getting all the records for selecting and editing is given below in steps:

1- Open SQL Server 2008 Management Studio
2- Goto Tools
3- Click "Options"

SQL Server 2005 error

How to fix?

Go to control panel >> Firewall Settings >> Add SQL Server’s Port to Exception List.

SQL Server not working-- Unable to connect to Management Studio in SQL Server 2005

On Yesterday I got a call from one of my post office saying that no applications are working . It shows an error that server is not exists. Firstly I thought that it is problem with network connections and I asked them to restart the server machine and try again but then also this error exists. I came to the office and tries to run the application. But seeing the error I thought that this problem with SQL server. On trying to open the SQL server 2005 management studio I got an error. The error is as follows

“A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider) “

First I wondered to see the error while connecting to server 2005. I never come up on such type of error during period as SA. While Contacting fellow Sys Admins they told that they had never come across such errors. While searching for the solutions on net But that not worked for me.

BACKUP to Node in Work Group Computers

For taking bakup in network location( ie in a client system) in WORKGROUP environment using sql server maintenance plan please do the following.

1. in the server , type services.msc in Run, select MSSQL Server, click on the logon Tab. Deselect Local system Account and Select this account. Type an admistrative user name and password which can access the shared folder in the specified client. 
ie., Server Administrator user name and password. For eg:- POSTMASTER, Administrator etc. 

AUTOMATIC BACK UP OF SQL 2008 EE DATABASE

Launch Management Studio and connect to the SQL server instance that contains the database that you want to back up. Right click on the database and then in the menu choose Tasks - Back up... This will open up a window where you can choose your backup options. Click on the "Script" button near the top and select the "Script Action to File" option. Save the File.
Now,ceate a Schedule Task to Run the Backup Script

Creating Maintenance Plans in SQL Server 2008 R2

One of the repetitive task that DBA need to perform is create maintenance plan for database. Maintenance plans enables you to automate maintenance activities for a database, backups, db integrity checks and index maintenance tasks. We can easily create a maintenance plan using a wizard in sql server 2008 R2.

You can use the following steps to create a maintenance plan

msdb Database Suspected\Corrupted-Solution (SQL 2000&2005)

One day I got a call from one of my offices that some programs ie point of sale is not working and the auto back up is not running. I reached the office and checked the server for any errors I found that msdb database is corrupted. I looked for the back ups then found that I have not planned auto backups for system database. I searched over the web to find a solution for the problem. I called to all my friends for solutions. One of my friend give me a solution that worked for me.

In Sql server 2000

you start the server with trace flag 3608.In SQL Server Enterprise Manager, right-click the server name, and then click Properties.

1. On the General tab, click Startup Parameters.
2. Add the following new parameter:
   -c -m -T3608
   

SQL SERVER - Not Starting (SQL Server 2000 Not Starting)

One day when I started the server I got a message. Microsoft SQL server not starting. While Restarting the SQL server it is not possible. Mostly SQL Server is not starting because master database is corrupted. Since SQL server is not started we cant restore the master database.

If you have SQL Server 2000 CD then you can restore the master database. Insert the  SQL SERVER 2000 CD. Then go to 

MY Computer-----

C DRIVE------Program Files-------Microsoft SQL Server-----------80-----------Tools----------Binn---------rebuildm.exe

Double click  on rebuildm.exe   then you have to show the path of DATA folder from the CD

(ie   Browse the CD  open the folder---*86--------DATA)

SQL Server Express

Microsoft SQL Server Express, a freely downloadable and distributable version of Microsoft's SQL Server relational database management system, comprises a database specifically targeted for embedded and smaller-scale applications.

Capabilities

  Unlike its predecessor, MSDE, it lacks a concurrent workload-governor to "limit performance if the database engine receives more work than is typical of a small number of users."[1] It has a number of technical restrictions (which make it unsuitable for some large-scale deployments) including:
Maximum database size of 4 GB per database (10 GB for SQL Server Express 2008 R2;[2] compared to 2 GB in the former MSDE). The limit applies per database (log files excluded); but in some scenarios users can access more data through the use of multiple interconnected databases.[citation needed]
No SQL Server Agent service
Hardware-utilization limits:
Single physical CPU, but multiple cores allowable[4]
1 GB of RAM (runs on a system with any RAM amount, but uses only at most 1 GB)
Although its predecessor, MSDE, generally lacked basic GUI management tools,[5] SQL Server Express includes several GUI tools for database management. These include:
SQL Server Management Studio Express
SQL Server Configuration Manager
SQL Server Surface Area Configuration tool
SQL Server Business Intelligence Development Studio.
Features available in SQL Server "Standard" and better editions but absent from SQL Server Express include:
Analysis Services
Integration Services
Notification Services

Source: Wikipedia

Scheduling of backup in SQL Server 2008 Express

  Sceduling of backups not possible in Sql server 2008 express editiion, because sql server agent is not present in sql express eidition. The daily back up of database is important in post office environments. A disaster plan is the type of document you hope you never need. But a disaster plan is a key element of systems administration strategy because of the risk of disaster presented by hardware failures, natural catastrophes, network intrusions, and human error. The risk of disaster is particularly high for databases.