June 2007 Archives

Ok, maybe I missed something but this seems like a long winding error that was easily resolved (and not in the manner the popup suggested) by simply starting the SQL Agent Service (made sense to me, I was trying to create a database maintenance plan, whether standard or with the wizard).

'Agent XPs' component is turned off as part of the security configuration for this server. A system administrator can enable the use of Blah blah blah blah blah'

Seems starting SQL Agent Service was the 'other solution' it meant :)

Powered by www.itgroove.net

Ok, ran across this one tonight when trying to enable the SSO account on MOSS 2007:

SSO Error: You do not have the rights to perform this operation.

In the end, I did two things (I think correctly) to fix this:

1. logged into the console using the account I wanted used for sharepoint SSO (I like RDP, thus used mstsc /console)
2. Set the Microsoft Single Sign On Account to use the account/password I wanted

Lots of docs from Microsoft and Adobe but this one is much shorter and sweeter.

http://www.joiningdots.net/blog/2007/05/sharepoint-2007-and-adobe-pdf.html

How to install Small Business Server 2003 in an existing Active Directory domain

Don't mind me. Needed to know today, so found out (thanks Avi.

I've had to do this on occasion and it was worth bookmarking. As well, there is more to considering renaming a SQL Server than just SQL or Windows.

If you just rename a SQL Server, SQL will bitch ... so here are the basics to be done ... (as well as checking logs, modifying backups, modifying antivirus clients and accounting for any other application/software that might be installed on the machine) - ie. there is a significant amount of 'other' things that will need attention besides SQL and the name change.

1. Ensure you have a recent and FULL backup of the server and SQL
2. Rename Server (follow appropriate naming rules and considerations for Active Directory)
3. After you change the server name and reboot SQL Server will automatically detect that you've changed the server name and then "fix itself". All you'll have to do is connect to the new server name in Query Analyzer and run the following command:
--- sp_dropserver 'old server name'
--- sp_addserver 'new server name', 'local'
4. Finally, delete the entry in Enterprise Manager for the old server name and add in the new server
5. Turn 360 degrees to the left, do two deep knee bends and shout 'Yoko killed the Beatles' 3 times

Some reference materials and gotchas (besides AV, backups, etc.) to consider:
-- Microsoft Technote for renaming SQL 2005 - same procedure applies for SQL 2000 - http://msdn2.microsoft.com/en-us/library/ms143799(SQL.90).aspx
-- Knowledge base references - http://support.microsoft.com/kb/303774/en-us, http://support.microsoft.com/kb/281642/en-us, http://support.microsoft.com/kb/317241/en-us

An oldie but a goody.

http://www.archive.org/web/web.php

Seems everytime I have to do this, I need to find the bloody syntax. So, here it is, so I can find it again fast next time :)

DBCC SHRINKFILE(DATABASE_NAME_log, 2)

http://support.microsoft.com/kb/272318/en-us

Powered by www.itgroove.net

DBCC SHRINKDATABASE (DATABASE_NAME, 10);
GO

http://msdn2.microsoft.com/en-us/library/ms190488.aspx

You may need to backup the transaction logs (and the database of course) in order to see the results you want...