Viewing 15 posts - 61 through 75 (of 6,102 total)
This is being executed by SQL Server, so it's going to use the SQL Server service account (not the Agent).
To use a different account, the easiest way to do...
December 16, 2013 at 8:02 am
Use procmon (http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx) to see what account is hitting that file. It'll need to run from the system where the Access database is. My guess is it's probably...
December 16, 2013 at 6:57 am
I wasn't speaking of SQL Server logins. If you go back up the thread, I was talking two Windows logins in different domains (in different forests) where there is no...
August 30, 2013 at 2:33 pm
Check what David said.
A member of db_owner, except for dbo, will honor a DENY on a table. Members of the sysadmin role map in as dbo, which effectively ignores the...
August 29, 2013 at 5:52 pm
Multi-tasking is bad! 🙂
August 29, 2013 at 8:04 am
The two accounts is a bit different than maintaining a separate admin account in development.
The main reason for the two accounts is to help reduce the risk of drive-by...
August 29, 2013 at 7:50 am
This is why I love Mladen's tool, especially if your servers follow a naming convention to define the environments. It allows you to build RegEx to color code the instances....
August 29, 2013 at 7:24 am
A great product for ensuring the proper color coding based on server name, for instance, is Mladen's SSMS Tools Pack. You can set the color and how big the visual...
August 29, 2013 at 6:54 am
If you allow access to the file system, realize that the SSIS packages will execute from wherever the dtexec command is given. So if it's given from the user's workstation,...
August 28, 2013 at 1:49 pm
I believe you can put in a server level trigger, but this should not be relied upon.
By the way, situations like this is one reason some folks put development...
August 28, 2013 at 1:42 pm
s.youngman (7/25/2013)
WayneS (7/25/2013)
[System.Data.Sql.SqlDataSourceEnumerator]::Instance.GetDataSources()
It's description is: "Provides a mechanism for enumerating all available instances of SQL Server within the local network."
So what I wonder is:
Does it only...
July 25, 2013 at 9:00 am
The concern is valid. It's a typical technique in spear phishing attacks.
By being stored, it won't affect SQL Server. SQL Server is not opening the document. I know that's...
July 1, 2013 at 7:25 am
If there are other DBs which are legitimately accessible by users, you can't.
If there aren't, and if you can authorization to modify your firewall policy on the server, then...
May 21, 2013 at 4:49 pm
If they're in a Windows security group, you can add the group as a login and deny permission to connect to the SQL Server.
However, this is usually seen as a...
April 30, 2013 at 11:08 am
Viewing 15 posts - 61 through 75 (of 6,102 total)