• HOME
  • STORE
  • CONTACT
Select the search type
 
  • Site
  • Web
Search
{3S} SQL Smart Security
Login|
Donate (EUR)
Donate (USD)
Facebook Twitter GooglePlus LinkedIn
You are here: FAQ

FAQ

Q1. ERROR: Network access for Distributed Transaction Manager (MSDTC) has been disabled. Please enable DTC for network access in the security configuration for MSDTC using the Component Services Administrative tool.

Created on: 3/28/2012; Modified on 3/28/2012;


Q2. ERROR: MSDTC on server 'PLACKO\SQLEXPRESS' is unavailable.

Created on: 3/28/2012; Modified on 3/28/2012;

About {3S} SQL Smart Security

Main Idea

In most cases, software companies deliver to their customers their heavily acquired know-how in the form of a database application logic as well.
This know-how in the form of a database objects content written in the T-SQL language is either fully open to read (ideal for industrial espionage), or they are satisfied with an integrated security level provided by a mass-spread database server such as Microsoft SQL Server.
There are plenty of tutorials, that can be found on the internet by a potential attacker, dealing with how to break the built-in security with the T-SQL keyword "WITH ENCRYPTION".
In such cases, less widespread, highly specialised, and even more so unexplored software products, such as {3S} SQL Smart Security, become highly topical.

Customer and Contact Information

Is {3S} SQL Smart Security For You?

  • Do you want to protect (to encrypt not only to obfuscate) your T-SQL know-how?
  • Are you familiar with work in IDE SQL Server Management Studio (SSMS)?
  • Are you unable to use encryption at the level of a whole database (TDE) or at the level of a file system (FSE)?

  • Issue Tracker
  • Blog
  • Forum
  • FAQ

Ing. MARIAN PLACKO, PhD.
Nitra, Slovakia

E-mail: 3s(at)placko(dot)eu
Personal Web: www.placko.eu

More Contact Information

Copyright 2012-2013 by Ing. MARIAN PLACKO, PhD. Terms Of UsePrivacy Statement