creating a view that auto-decrypts the data makes the data no longer HIPAA compliant, doesn't it?

I'd say that is no different from storing the data unencrypted in the first...

hmmm; i'd say there is always files that can be moved or deleted.

files in temp folders on the operating system, log files, , the already suggested moving of backup files,...

This looks an awful lot like homework, so I'll frame my answer with that in mind.

It looks like the purpose of this exercise is to learn how to use the...

do a find and replace to add QUOTENAME, so you can accommodate weird database names with dashes/spaces

FROM '+@pDatabase+'

--should be

FROM '+ QUOTENAME(@pDatabase) +'

i think you want DataGridView.Visible = false; enabled would be more like displaying, but removing editablity due to permissions or something.

visible is what you need to hide/show

aaron i'm sure you know that SQL doesn't order data in any specific order without an explicit ORDER BY clause.

in your case, i'm thinking you might do what you...

Blair Dee-474691 (4/29/2013)

---

hey thanks for the tip. I did download and install that and it looks like it will generate the script to copy the data over but it...

since the accessing of data is done after the login, the log isn't going to help you.

you would need to add a new level of auditing to capture those...

ok here's my version, which i adapted from a DDL trigger i made for another post.(add new objects to this role)

this will generate three roles, one for each requirement, then...

actually, both powershell and ssms are using smo under the covers.

the batch separator is an option you can select, i believe.

see this thread for an example on teh same question:

http://www.sqlservercentral.com/Forums/Topic996028-1351-1.aspx#bm996236

also check out this neat trick:http://sev17.com/2011/10/22/gaining-sql-server-sysadmin-access/

basically it's a model for a SQLCMD script which would add a new sysadmin user, because it is able to run as the built in...

it's just the wrong provider;

jet is for 32 bit Access/Excel, and not for SQL Servers.

here's your command adapted, and also one I know works for sure:

--query directly without open rowset:

SELECT...

convert to...

collation.

for case insensitive searches, some high ascii characters are treated as the same character as certain low ascii.

you can use an explicit binary collation, for example, which would seperate teh...

remove the SET IDENTITY_INSER

%T command. since it is not valid/has no effect with BULK INSERT statements.

instead, as identified, you need to add KEEPIDENTITY to your BULK INSERT command:

BULK

INSERT ABC

FROM...