November 26th, 2008 by Gabriel

Single User mode allows only one single user to connect to the database.
Even if SQL server is in Single User Mode, you can connect the SQL Query Analyzer with the SA user.

Single user mode specifies that only one user at a time can access the database. Basically it is used for maintenance purposes.

If any other users are connected to the database and you  switch the database to single user mode then their connections to the database will be closed without any warning message.

Following are the steps to start SQL server in Single User mode -

On your server :

Start >> Run >> type in CMD and hit Ok >> it will open up Command Prompt >> here execute the following command

net stop MSSqlServer

>> it will stop the SQL service >> now to start SQL in Single User mode execute following command

sqlservr -m

####

How to Set a single database into Single User Mode :-

You can set a single database into single user mode using an alternative procedure but this process cannot be used to set the MASTER database into single user mode.

# Connect to SQL Server using SQL Query Analyzer with SA user

# Execute the following command -

alter database database-name set SINGLE_USER

where “database-name” is the actual name of the database.

This cannot be used to place the databases MASTER, MSDB or TEMPDB in single user mode.

# To set the database back into normal multi-user mode use, execute the following command -

alter database db-name set MULTI_USER

November 24th, 2008 by Gabriel

A connection string is a string which contains information about a data source and its connectivity.
Connection string is always passed to a driver or provider which initiate the actual database connection.
It includes the attributes like name of the driver, server/host address, database name, security information like user name and password.
The format of a connection string is a semicolon-delimited list of key/value parameter pairs.

Following is a sample SQL database connection string :-

<add name=”SampleConnectionString” connectionString=”Data Source=AAAAAA;Initial Catalog=BBBBBB;User ID=CCCCCC;Password=DDDDDD” providerName=”System.Data.SqlClient” />

Where :
AAAAAA : Your server’s actual IP address.
BBBBBB : Your database’s actual Name.
CCCCCC : Your database’s actual Username.
DDDDDD : Your database’s actual Password.

October 26th, 2008 by Gabriel

100% of CPU usage by Csrss.exe

Csrss stands for client/server run-time subsystem which is essential and must be running all the times.
It is responsible for console windows, creating and/or deleting threads etc.
The csrss.exe file is located in the folder C:\Windows\System32, if you find it at any other location then it may be a virus or spyware.
Csrss.exe process manages most graphical commands in Windows which is important for the stable and secure running of computer.

Whenever Csrss.exe utilizes 100% of the CPU on right clicking an item in Windows Explorer or on the desktop then it may be an issue with user profile, it may be corrupted.

Fix :-

First of all take the complete backup of your “My Documents” folder and all important data stored in your profile.
Log in with an account which has administrative privileges and open the user profiles list.
To retrieve the list of local user profiles right click on “My Computer” icon and select Properties,
click on Advanced tab,
click Settings under User Profiles,
select your profile from the list, and then click Delete.

Logoff, and then log back on as yourself. A new profile will be created when you log on.

October 12th, 2008 by Gabriel

Some basic security policies that a Web Administrator should have to consider are -

1. who/which user is allowed to use the system
2. when the user is allowed to use it
3. which user granted which level of access
4. procedures for granting access to the system
5. remote and local access methods
6. system monitoring
7. suspected security breaches

If you don’t have a clear picture of what is permitted, you can never be sure when a violation has occurred.

General security precautions to take -

1. Limit the number of login accounts available on the machine and delete inactive users.
2. The Crack programs help to detect poorly chosen passwords hence force the people to use strong             passwords who have login privileges.
3. Unused services should be turned off. For e.g. if FTP is no longer needed then it should be stopped.
4. Check system regularly for suspicious activity.
5. Make sure that permissions are set correctly on system files.