I had someone ask me for a comprehensive list of configuration options for an x64 SQL Server install. besides just SQL config options, they were also looking for info on OS settings (server 2003 in particular).
i know where we could get bits and pieces of the information, but does any provide a comprehensive type list?
does anyone know of any security risks with the default PUBLIC settings for sql 2005/8?
i ran sp_helprotect and it listed out the PUBLIC grants, and now i have an auditor telling me that i have a security risk because PUBLIC has access to system information. before i start to present my case i wanted to see if anyone has any links or information they can provide that would detail how the default settings allow for a security risk.
for the record, the auditor mentioned that these setting allow for the ability to crack passwords because they can view the password hash. i have not been able to verify that the setting allow for such an ability to see that information through the sys catalog views.
thanks in advance
What are the benefits to using virtual as opposed to running multiple instances of SQL on a box?
I have a colleague that is looking for help with the following situation. If anyone can be of assistance, it would be appreciated. Thanks.
From his email:
A couple of months ago, the admin spent quite a bit of time installing SCCM as a pilot. (We have no experience with System Center here prior to this.) Because it was a pilot and on a test box, he installed it using our domain's Administrator account, which still was called "Administrator", and had not added any other admins. About a week ago, our admins completed a project to change the name of Administrator domain-wide to something else to improve our domain security. Unfortunately, because this system is in test, it was missed during the systems review, and we can no longer administer SCCM.
The best possible scenario would be to find a way to get System Center to recognize the new name of Administrator so we can administer SCCM. The only solution we've found on the Internet is to completely reinstall it, which our admin is reluctant to do because of the time invested in installing and configuring it - he was getting close to rolling it out companywide. I know it's a long shot, but I thought you might know of something anecdotal that might be able to help us, or that you might know of someone else you could refer me to.
other than staring at a clock on the wall, is there any good technique for measuring the effects of various soft-NUMA configurations for SQL?
What we are hoping to show is the performance edge gained (if any), but I was hoping to show more details than just "it used to take an hour, now it takes 48 minutes", because that is not enough proof (in my opinion) that our NUMA changes were the reason for the gain.
If there is a way to measure and decipher some output I would be most interested in hearing about them, thanks.
my understanding of the ghost cleanup process is that every five seconds it will look to removed ghosted records in an index. and so it will not overload the system, it will only "clean" roughly ten pages at a time.
so, that means it only cleans roughly 80k worth of records every five seconds? seems like my indexes would always be filled with ghosted records and the cleanup would never finish.
so, let's say i run a delete, perhaps a million rows, and the index records for those millions rows are roughly 8Gb in size. so roughly 100,000 times the difference of 80k. does that mean the ghost cleanup process will take 500,000s, or almost six days to complete?
clearly i am missing something here, because it does not make sense that it would take that long to clear out the ghosted records. and what about the other activity that hits that same index? does the ghost cleanup process cause waits, or have to wait for other processes?
[this question brought about by performance issues we have been seeing in the OpsMgrDW and we wanted to know more about this process]
i am looking for some custom scripts to pull information on perfomance data counters being collected by OpsMgr. Does anyone have any scripts they are currently using?
Is there a way to register a server to your CMS and use SQL Authentication?