Viewing 15 posts - 1,051 through 1,065 (of 6,105 total)
It can be done remotely, but if you disable the network libraries, you will have to do it local.
SSMS can do it, but you can't make the initial connection with...
June 13, 2008 at 1:29 pm
You may have to disable the network libraries temporarily so that the only connection that can be made is from the local server. You can do that through SQL Server...
June 13, 2008 at 12:40 pm
brewmanz.sqlservercentral (6/12/2008)
June 12, 2008 at 10:23 pm
To expand upon what was said...
SQL Server can handle two types of logins:
- SQL Server logins
- Windows logins
SQL Server logins are the ones where the username and password combinations are...
June 12, 2008 at 10:19 pm
As Andras has already indicated, no. SQL Server figures the true database owner should not be blocked from anything. As a result, it does NO security checks within the database.
You...
June 12, 2008 at 10:13 pm
If it's truly an AccessViolationException error, that's not a connection problem. The application is trying to do something with protected memory in a way it shouldn't (this isn't to say...
June 12, 2008 at 10:10 pm
If you want to view data, in the database, adding the user to db_datareader will allow SELECT to run against tables and views. It will not permit EXECUTE for stored...
June 12, 2008 at 10:08 pm
By default, all three logs (application, security, system) are rather small. If you have any kind of auditing turned on, the security log rolls over very, very quickly. We have...
June 12, 2008 at 10:00 pm
You've got 2005 Enterprise Edition, meaning you have the online restore, index rebuild features. Therefore, if you put it in one database, you have the option, in some cases, of...
June 12, 2008 at 12:38 pm
Not through a stored procedure or anything like that. Are you switching domains? If so, you can probably script the permissions assigned directly to various Windows logins and re-apply them...
June 12, 2008 at 12:33 pm
Here's how to recover. It'll require you to bring your SQL Server off-line:
Disaster Recovery: What to do when the SA account password is lost in SQL Server 2005
June 12, 2008 at 12:29 pm
SSWUG.com asked a similar question. Since I'm primarily security focused, that was most prominent on my mind. Here's the list I sent them in an email:
Membership of the local Administrators...
June 12, 2008 at 11:53 am
okkko (6/12/2008)
June 12, 2008 at 11:49 am
Perry Whittle (6/12/2008)
our databases all get set to SA ownership and SA has a secure password.
And that's a standard practice. The reason to do different owners is to prevent ownership...
June 12, 2008 at 11:46 am
You want to use SQLPing. Have a domain admin run it.
The registry option only works if you know to connect to the SQL Server. SQLPing will use all...
June 12, 2008 at 11:34 am
Viewing 15 posts - 1,051 through 1,065 (of 6,105 total)