” Hello Earth! Greetings from the STS-43 Crew. This is the first AppleLink from space. Having a GREAT time, wish you were here,…send cryo and RCS! Hasta la vista, baby,…we’ll be back! ”
to Marcia Ivins, a shuttle communicator at Johnson Space Center. The AppleLink software was configured with a special Macintosh Communications ToolBox Connection Tool that interfaced to NASA’s communication system which allowed the Shuttle to call up GEIS’ network from space. The Shuttle’s e-mail address was secret, but exposed to GEIS’ e-mail network as any other AppleLink address. To avoid a deluge of incoming mail resulting from the publicity of the event, Apple set up a number of obvious “honeypot” addresses not really used by the Shuttle crew, such as STS43@APPLELINK. Most of the well-wishers’ e-mail went there, rather than to the real Atlantis address.

See for yourself if your SQL installation is bad, try the SP reinstall and sections will fail due to missing packages. 

HAve maintenance plan failures when creating a new plan?  Invalid column name ‘from_msx’.
Invalid column name ‘has_targets’. (Microsoft SQL Server, Error: 207)
SELECT SERVERPROPERTY(‘ResourceVersion’) as ResourceDB, SERVERPROPERTY(‘ResourceLastUpdateDateTime’) as ResourceDBLastUpdate,

SERVERPROPERTY(‘ProductVersion’) as Ver, SERVERPROPERTY (‘ProductLevel’) as SP;

GO

If your results show a Resource DB version that is different than your SQL Version, then you have a messed up install, probably due to the SP not installing correctly.  Ensure you have your windows\installer directory,  luckily I saved mine to another drive in case I needed it again.  Also check to make sure your permissions are right on where your SQL DBs are at.  Make sure your SQL local groups contain the correct user for which the SQL AGent and server are running as.

Keep your other sys db’s with Master!
ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=data, FILENAME= “R:\sqldata\mssqlsystemresource.mdf”)
ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=log, FILENAME= “S:\sqldata\mssqlsystemresource.ldf”)

backup the database
shrink the logfile
use sp_detach_db to detach the database
move the logfile to the new drive
use sp_attach_db to reattach the db

Reducing a transaction log that is already in simple mode:

USE DatabaseName
GO
DBCC SHRINKFILE(, 1)
BACKUP LOG WITH TRUNCATE_ONLY
DBCC SHRINKFILE(, 1)
GO

note: if your db has hyphens (-), you need to use  ‘  or you need to use ” depending on command

EXAMPLE:

USE “DB-WITH-019503950-HYPHENS”
GO
DBCC SHRINKFILE(“DB-WITH-019503950-HYPHENS_LOG”, 1)
BACKUP LOG “DB-WITH-019503950-HYPHENS” WITH TRUNCATE_ONLY
DBCC SHRINKFILE(‘DB-WITH-019503950-HYPHENS’ 1)
GO

Moving Sys DBs and Logs

NOTE YOUR TARGET DIR FOR NEW SQL SYS DB’S should match the security for NTFS, ie, you need the sqluser group from the local machine added with full control or your startup param will be denied access to the new directory!

start SQL Server together with the -c option, the -m option, and trace flag 3608

In SQL Server Enterprise Manager, right-click the server name, and then click Properties.
On the General tab, click Startup Parameters.
Add the following new parameter:
;–c-m-T3608 at the END of the text

make sure agent is shutdown prior to this and also close out of any connections to the DB, or you will get access denied no matter what ID you use

In 2005,  use SQL Server configuration Manager, choose SQL 2005 Services, click on Advanced, scroll down to startup parameters,

select “Startup Properties” and the following window will pop up

separate entries with a semicolon, so your first entry now is your switch to start in single user mode, quickly and with trace flag 3608:

;–c-m-T3608 at the END of the text

stop and restart SQL, make sure sqlagent is shutdown, check event log for 17658 event ID for the sql server starting in single user mode

 if this fails, use the net stop mssqlserver

NET START MSSQLSERVER /c /m /T3608

after this launch the mgmt console and make sure you close object explorer or you’ll get an error about how many users can login

“SQL SERVER is in SINGLE USER MODE and only one administrator can connect”
By default the object explorer is open and it is considered as one connection so if you click new query it is considered as second connection and hence you get the error. Inorder to avoid the error you need to click the disconnect button in the object explorer pane and then close the object explorer window.Now you could see this window as “No Server Connection”,

choose file/close object explorer

 if you did that and still happens, then you need to ensure that all odbc connections on sql ports are shut down, check your other servers and make sure they  aren’t connecting to the server

Edit the Startup Parameters values to point to the planned location for the master database data and log files, and click OK. Moving the error log file is optional.
The parameter value for the data file must follow the -d parameter and the value for the log file must follow the -l parameter. The following example shows the parameter values for the default location of the master data and log files.

If the planned relocation for the master data and  and S for log files the parameter values would be changed as follows:

-dR:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf;-eF:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG;-lS:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf

Stop and then restart SQL Server.
Detach the model database by using the following commands:

use master
go
sp_detach_db ‘model’
go

Move the Model.mdf and Modellog.ldf files from the default folder to the new folder path.
Reattach the model database by using the following commands:

SP_DETACH_DB ‘MSDB’
GO
SP_DETACH_DB ‘MODEL’
GO

sp_attach_db model, ‘E:\Sqldata\model.mdf’,’E:\Sqldata\modellog.ldf’
sp_attach_db msdb, ‘E:\Sqldata\msdbdata.mdf’,’E:\Sqldata\msdblog.ldf’

don’t copy and paste from here, type it out or it won’t translate

Remove -c -m -T3608 from the startup parameters in SQL Server Enterprise Manager or in SQL Server Configuration Manager.
Stop and then restart SQL Server. You can verify the change in file locations by using the sp_helpfile stored procedure.

use model
go
sp_helpfile
go

all others refer to http://support.microsoft.com/kb/224071

MOVING TEMPDB

use