Bur remember, you need to restart the sql server before the change is implemented.

The prblem is not that Administrator didn't have permissions on the file,

but that the Hotfix installation was started under an account which is not an administrator on the server.

Otto,

the replication you're dealing with is transactional replication. With transactional replication transaction are kept in the logfile until they are succesfully applied at the subscriber. For some reason in...

Sorry, but SQL 2000 doesn't have this functionality. Only options in 2000 would be running a trace or use a third party auditing.

I think you're looking for this:

EXEC master.dbo.sp_readerrorlog

You need to rebuild the master database in order to change the server collation.

http://technet.microsoft.com/en-us/library/ms179254.aspx

Sorry, I forgot to exclude the system objects in my previous query. These are queried everytime you open Object Browser in SSMS it won't help you at all. So here's...

If it's just to check if a database is still actively used you can also use the sytem view sys.dm_db_index_usage_stats to track database activity.

This view has columns to track...

You need to attach the database either through SSMS or using the sp_attach_db stored procedure.

Disabling a Login will prevent the users to logon. Existing connections you need to Kill, just like it's done in the article about logon triggers.

The fact that you say that the maintenance plan only does things for certain databases makes it difficult to make it dynamic. But if you have some common way of...

LOGON_Triggers would be one way to go and you can find a good article about how to do it here[/url].

Another option would be creating a job which disables the login(s)...

Yes, SQL 2008 Express Edition does have support for Filestream data and as far as I know the 4 Gb limit does not apply to Filestream data.

Just like temp tables, table variables are physically stored in the tempdb. So the values returned by sys.fn_PhysLocFormatter should point to the file, page of the tempdb.

After the prerequisets get (.Net 3.5 and Windows Installer ) installed you need to reboot your system. After the reboot run the setup again and this time it should go...