if you receive the following message, read on..

Msg 15281, Level 16, State 1, Procedure xp_cmdshell, Line 1

SQL Server blocked access to procedure ‘sys.xp_cmdshell’ of component ‘xp_cmdshell’ because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of ‘xp_cmdshell’ by using sp_configure. For more information about enabling ‘xp_cmdshell’, see "Surface Area Configuration" in SQL Server Books Online.

Start a SSMS (Microsoft SQL Server Management Studio), open a New Query Window and do the following:

Paste this and execute it using F5

EXEC sp_configure 'show advanced options', 1
  GO 
 
RECONFIGURE
  GO 
 
EXEC sp_configure 'xp_cmdshell', 0
  GO 
 
RECONFIGURE
  GO

to check if it’s configured properly, use this extended stored procedure:

xp_cmdshell 'dir *.exe'

Save
Saving changes is not permitted. The changes you have made require the following tables to be dropped and re-created.  You have either made changes to a table that can’t be re-created or enabled the option Prevent saving changes that require the table to be re-created.

Here’s a screenshot:

In the 2008 , they have added a new option to prevent saving of changes that will require a table re-creation.  If you think about it, this is a good thing.  If you are running a production database, you want maximum performance.  If Management Studio needs to re-create a table to apply a change that means it needs to create a copy of the table, transfer the data, create the new table, move the data over, delete the old stuff, etc.  This can potentially be a major operation. 

However, if you don’t want this feature enabled or our just working with a development or test database, it is easy to turn off.  Just open up the Options window in Management Studio and go to “Designers –> "Table and Database Designers”, find the “Prevent saving changes that require table re-creation” option, and turn it off.

Code (SQL Statement) starts here

select *
from master..sysprocesses
where loginame = ‘connexin.cim’ –and hostname=’COMPUTERNAME’
order by hostname

Code (SQL Statement) ends here

if you want to drop connections to a specific database, check this post

No Management Studio installed? Just use osql.exe to connect to the database server.. here’s an example ‘how to connect to Microsoft SQL using osql.exe’

Code starts here

use master
declare @vcdbname varchar(50)
/* @vcdbname => set it to the database you want the connections to be dropped.. */
Set @vcdbname = ‘cxnIM’

set nocount on
declare Users cursor for
select spid
from master..sysprocesses
where db_name(dbid) = @vcdbname
declare @spid int, @str varchar(255)
open users
fetch next from users into @spid
while @@fetch_status <> -1
begin
   if @@fetch_status = 0
   begin
   print @spid
      set @str = ‘kill ‘ + convert(varchar, @spid)
      exec (@str)
   end
   fetch next from users into @spid
end
deallocate users

and ends here

Assuming you have an MDF file called cxnMassImport.mdf and you want to attach it using osql.exe.

Open a CMD

Type:

osql.exe -E -S .\SQLExpress

If you don’t have osql.exe on the system, you can just copy it from an SQL Server to your system. Osql.exe can (usually) be found under
%ProgramFiles%\Microsoft SQL Server\90\Tools\Binn\OSQL.EXE (for a SQL 2005 Installation)
%ProgramFiles%\Microsoft SQL Server\100\Tools\Binn\OSQL.EXE (for a SQL 2008 Installation)
All of the osql.exe’s dependencies (DLLs etc) exist on a more or less default Windows setup.

The used osql.exe syntax for this example is:
-E => Trusted Connection – means your currently logged on user credentials are used to do the connection to the SQL Server

-S => Servername and Instance. Use a dot for the local system. If your SQL Server is some kind of MSDE or SQL Express Version, you must provide the Instance Name. For SQL Express it is usually SQLExpress. To find out the Instance Name, go to Services.msc and check the SQL Server Service. See the value between the ().

Services_SQLServer(Instance)

To connect to the SQL Server Instance using SQL integrated security, use the -U for the username (sa) and -P for the password.
i.e.

osql.exe -U sa -P P@ssW0Rd -S .\SQLExpress

Now to attach the MDF file, on the osql.exe prompt write:

sp_attach_db @dbname='cxnMassImport', @filename1='C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\cxnMassImport.mdf'
GO

osql_sp_attach_db

To verify if the database has been attached write:

SELECT name, filename FROM sysdatabases WHERE name LIKE '%cxn%'

Osql_SELECT_Name_Filename_FROM_SysDatabases

If you need to detach the database, write:

sp_detach_db @dbname='cxnMassImport'

short description:
use SECURITYMODE=SQL as command line setup parameter when installing SQL Server
or
change one of the following registry keys:

Default instance:
HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode

Named instance:
HKLM\Software\Microsoft\Microsoft SQL Server\ Instance Name\MSSQLServer\LoginMode

to 2 for mixed-mode or 1 for integrated security. (Integrated is the default setup for the SQL Server 2000 Data Engine.)

for more refer to article MS Q285097

try this, maybe this solves the issue..

a. Stop all SQL Server services (MSSQLServer, SQLServerAgent, MSSEARCH)
b. Open command prompt and go to the %ProgramFiles%\Microsoft SQL Server\80\Tools\Binn directory
c. Unregister the following .dll files (Ex. regsvr32 /u dtsui.dll): dtsui.dll,sqlns.dll, sqldmo.dll, sqllex.dll, sqlmmc.dll
d. Copy and paste the .dll files from a CD (under x86\Binn directory) to the Program Files\Microsoft SQL Server\80\Tools\Binn
e. Register the .dll files (Ex. regsvr32 sqldmo.dll)