see this:

http://msdn.microsoft.com/en-us/library/ms187965.aspx

shrinking file will reduce free space...

try to ping the server using the machine name. If you are unable to ping, its a DNS issue.

besides IP, you can also use FQDN to connect.

sp_configure is used to read/change server wide settings.

sp_dboption is used to modify database level properties (not specific to a particular mdf or ndf).

so when you use sp_dboption to auto shrink...

It will return if either of the operands have null. You said you are using isnull, but the code you have shown doesnt have that.

Right click your server in management studio, goto properties. In the properties window, goto security and change authentication mode.

You'll need to recycle SQL Server services after that.

Are you connecting from the same server where SQL Express is installed? If not, remote connections are disabled by default on SQL Express. You'll need to enable that.

Also, Try connecting...

And make sure the service account has write privileges on the UNC path.

Hope you have enabled the trace flag 1222 suggested by Gail. Whenever deadlock occurs, it'll be written in the SQL Server's error log.

Each resource group (instance) will have a distinct IP. Users will view each instance as a virtual...

select * from sys.sysprocesses where dbid=db_id('my_db')

are you using a connection in query window? if yes close that and then try.

you can also query sys.sysprocesses to check who is connected to that database.

find the spid of the long running query and kill it

kill spid

Joy Smith San (11/9/2011)

---

Secondly for testing purpose, I configured my local sql server to use MIN memory as 1024 MB. But when I restarted it's using hardly 90 MB it...

You can backup your log but it wont truncate if log truncation is waiting for replication.

If the recovery mode is full, schedule regular log backups. See if transactional replication...