I used to work with Oracle ETL/database tools and now I have transferred to a Microsoft working environment. In Oracle SQL Developer there was a feature named Data Masking which would mask selected column values with *** characters. Is this also possible with Microsoft SQL Server 2016?
As others commented, you are probably looking for Dynamic Data Masking which is available in all versions of SQL Server 2016 SP1, even Express and the embedded LocalDB. The equivalent in Oracle is Data Redaction
You'll find a nice overview in Use Dynamic Data Masking to obfuscate your sensitive data
Related
I see SQL Server 2016 SP1 All Editions now have "Always Encrypted" available. From looking around, it appears there's a new ODBC driver that will work with the "Always Encrypted" data.
With the caveats in the SQL Server documentation about working with encrypted columns, does anyone have experience using this encryption with Microsoft Access? Will it work with Access 2010, or does it require newer versions?
Is there a noticeable performance hit from the encrypting/decrypting? Am I reading it right that since joins and where clauses require additional handling for encrypted columns, best practice would be to not use sensitive columns as keys.
Also, I have an Access Project -- can this work with Access 2010 in a Project (adp), or will I have to update to an .accdb version of the application?
Here is a post with a solution on how to configure Access with Always Encrypted: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/b9eea19c-1943-4b25-b07d-9193f7b7dab0/odbc-always-encrypted-problems?forum=sqldataaccess.
i just want to know about the best way to store sensitive and secured data in wpf application that will not appear inside the exe file like databases and will store data and retrieve it when program start up again
Going by the latest comment, it seems that you need to encrypt user input data. Depending on the size of the data you could go with SQL Server 2008 R2 Express or SQL Server Compact. You can have a look at SQL Server 2008 R2 CE encryption or SQL Server 2008 R2 Express encryption.
If you are not looking at databases, then you could have a look at file based encryption using the System.Security.Cryptography namespace.
Higher levels of security are available in the enterprise version of SQL Server. More information on encryption levels in SQL Server 2008 can be found here.
Note that encryption of the database (depending on the algorithm used) can negatively affect the performance.
Has anyone here moved the database underlying a SP 2010 install from one database instance to another (same data, just hosted in another instance)?
For example. we just want to move the database to a diffrerent machine.
In addition, has anyone moved SP 2010 from using SQL Express to a higher version of SQL Server? I would like to run some proof of concept tests with SQL Express, and if all goes well, then move to SQL Standard or Enterprise.
Cheers,
Daniel
Check out the following article:
http://technet.microsoft.com/en-us/library/cc512725.aspx
I don't think you'll run into any problems, just make sure you aren't going backwards in versions between databases. Backing up a database in SQL Server 2008 and restoring in 2005 isn't easy.
I've never done this with SharePoint, but I believe it lets you specify the location of the configuration database. Then you just need to match the user permissions.
The TechNet article "Move All Databases (SharePoint 2010)" is your main guide.
Note that this article contains the following warning:
The new database server must be running the same version of Windows
Server and Microsoft SQL Server as the existing database server.
This in NOT true!
Both from my own experience in migrating SharePoint databases and talks I've had with Microsoft Primary Field Engineering, I can say this method also works when SQL Server versions differ. But only if you upgrade to higher SQL Server versions (i.e. SQL Server 2005 to SQL Server 2008 R2). I was told this scenario is also fully supported by Microsoft.
Also, don't forget to update the database compatibility level for the migrated databases. This should future-proof your databases and enable advanced SQL Server optimization.
Does anyone know of a tool similiar to RedGate's SQL Data Compare that works with Microsoft SQL Server Compact 3.5?
For me the following process worked:
Install SQL Server Compact Toolbox extension.
Run the "Script database schema and data" command on both databases
Use a diff tool on generated files to see the changes.
In the end I solved this problem by Exporting my 2 SQL Server Compact Databases to SQL Server Express 2005 (although 2008 would work) using Data Port Console.
I then compared them using Red Gate SQL Data Compare.
This solution works just fine for me.
Not sure, but you could also have a look at the Apex SQL tools - Apex SQL Diff and Apex SQL DataDiff. There website is here. They don't specifically mention SQL Server Compact - but I'm sure you could inquire with them.
Red-Gate and Apex are my #1 choices for any kind of SQL tools :-)
Marc
Have you tried SQL Compare from starinix? They say it supports SQL Server (All Editions) so that may include compact edition.
This software does work as I have used it (for Yukon). It's also freeware which saves worrying about licensing.
We're upgrading an existing program from Win2k/SQL Server 2k to Windows 2003 and SQL Server 2005 as well as purchasing a new program that also uses 2k3/2k5. The vendor says that for us to host both databases we need to get the Enterprise version because the softwares clients use different collation for the connections and only Enterprise supports this.
I cannot find anything on MS's site to support this and, honestly, don't want to pay the extra for Enterprise if the Standard edition works. Am I missing some not talked about feature of SQL Server or is this, as I suspect, a vendor trying to upsell me?
All editions of SQL Server 2000/2005/2008 support having multiple databases, each using their own collation sequence. You don't need the Enterprise version.
When you have a database that uses a collation sequence that is different from default collation for the database server, you will need to take some extra precautions if you use temporary tables and/or table variables. Temp tables/variables live in the tempdb database, which uses the collation seqyuence used by by the master databases. Just remember to use "COLLATE database_default" when defining character fields in the temp tables/variables. I blogged about that not too long ago, if you want some more details.