Tag Info

New answers tagged

0

It's possible to move a private key from one server to another, if the symmetric key was created using a certificate. The certificate is what allows you to create the same symmetric key on a different server. Looks like that is your approach so you are off to a good start. You have created a symmetric key, secured with a certificate, to encrypt a column of ...


0

Looks like you did not encrypt the encryption key with the database master key. There has to be a complete chain from the service master key to the encryption key, usually is like this: service master key -> database master key -> [optional certificate private key] -> encryption symmetric key You are going to have to open the encryption key using the ...


0

I have dealt a lot with PCI and HIPAA recently since we've developed the ApexSQL Audit compliance tool (some details about the tool can be found here), and during a few years of working on the tool and demoing the tool, I was engaged in numerous discussions about the status of DBA in relation to compliance rules. PCI and HIPAA are not developed to deal with ...


1

If your MySQL client/server version is a 5.6.x a way to avoid the WARNING message or putting a password in command line, you can use the mysql_config_editor tools: mysql_config_editor set --login-path=local --host=localhost --user=username --password Then you can use in your shell script: mysql --login-path=local -e "statement" Instead of: ...


1

Turns out the answer is actually to use the -p -- the long version allows you to set it to empty, like so: mysql --port=3307 --host=127.0.0.1 -uroot --password=


0

You don't need to export or import anything. As long as the versions of MySQL on both machines are identical you can simply Shutdown MySQL process service mysql stop Overwrite the installed /var/lib/mysql with the old /var/lib/mysql. A. cp -Rf /var/lib/old_mysql /var/lib/mysql B. As a precaution you could move the /var/lib/mysql on the new server mv ...


1

HeavenCore's reply answers the question. However there is another way to get around this without security flaws. Return output to a table, query the table with DBmail.


0

If "watch the history log to see if the job completed" can be accomplished by using either a stored procedure, scalar function, or table-valued function (as opposed to direct SELECT access to the msdb.dbo.sysjob* tables), then you can get away without granting any permissions at all to any real Login/User that will be logging in. You will still create at ...


0

To be able to check all jobs you would need go add the user to the SQLAgentReaderRole in the msdb database which also gives that user permission to create jobs. To minimize the access granted you can also grant the user select permission on the tables used by the sql server agent


8

You could create a domain group that you could use to create as login and user on your SQL Server and YourDatabase. After creating the domain group, you could do something like: USE [master] GO CREATE LOGIN [DOMAIN\AllUsersForYourDatabase] FROM WINDOWS GO USE [YourDatabase] GO CREATE USER [DOMAIN\AllUsersForYourDatabase] FOR LOGIN ...


0

I see only 2 options to get it to work : Application inserts value for password field Table has NULL or default value for password field If the column allows NULL, that should be enough, right? If you want it to have a value, having the application insert it, across the network, is probably riskier, than setting a default value in the table. Setting the ...


1

I was going to just comment the link to the SQL Server 2012 Best Practice security white paper...but found out Microsoft took it off the Internet for some reason. You might be able to find a cached version of it some where online, but I will paste in the contents of contained database section of the document here. There is also a BOL article for Security ...


1

A user must have a security context to access the ReplData database. That can be their own account, an AD group of which they are a member, or the guest user (if the guest user is enabled in the ReplData database). No permission need be granted on the ReplData.dbo.refData table as long as the ownership chain is unbroken. Since the refData table is owned ...



Top 50 recent answers are included