Re: Change in SQL functionality between 7 and 2k

From: Dan Guzman (danguzman_at_nospam-earthlink.net)
Date: 09/27/03


Date: Fri, 26 Sep 2003 21:50:40 -0500


The ENCRYPT function is not documented in SQL 7 or 2000, AFAIK. As
such, Microsoft can change or remove the function without notice. If
you choose to use undocumented functionality, you do so at your own risk
because changes may be made between versions or service packs without
notification.

> I am in the process of replacing it
> with more secure methods (if I can get the rest of my
> company on-board)

This is certainly a good idea.

-- 
Hope this helps.
Dan Guzman
SQL Server MVP
-----------------------
SQL FAQ links (courtesy  Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
-----------------------
"James" <James@south.africa> wrote in message
news:081601c3845e$b9730120$a301280a@phx.gbl...
Hi,
Does anyone know why MS changed the way that the ENCRYPT
('message') function works?  I am in the process of
replacing an old authentication method which uses this
function because it works differently between SQL 7 and 2K.
Here's an example: on my computer I have SQL 7 running
alongside a SQL 2K instance.  I execute exactly the same
statement against both instances. SELECT CONVERT(VARCHAR
(20), encrypt('mysecret'))
In SQL 7 I get what I expect: bSLL&#8217;v4
In SQL 2K I get a unicode translation in clear text:
mysecret or something similar.
I have found no info about this in technet or in the
product info for 2000. I am in the process of replacing it
with more secure methods (if I can get the rest of my
company on-board) but I still want to know what changed
and why the chage wasn't documented.


Relevant Pages

  • Re: Change in SQL functionality between 7 and 2k
    ... The ENCRYPT function is not documented in SQL 7 or 2000, ... > with more secure methods (if I can get the rest of my ... product info for 2000. ...
    (microsoft.public.sqlserver.security)
  • Re: Change in SQL functionality between 7 and 2k
    ... Thanks Dan, ... >> with more secure methods (if I can get the rest of my ... >SQL FAQ links: ... >replacing an old authentication method which uses this ...
    (microsoft.public.sqlserver.security)
  • Change in SQL functionality between 7 and 2k
    ... replacing an old authentication method which uses this ... function because it works differently between SQL 7 and 2K. ... product info for 2000. ... I am in the process of replacing it ...
    (microsoft.public.sqlserver.security)
  • Change in SQL functionality between 7 and 2k
    ... replacing an old authentication method which uses this ... function because it works differently between SQL 7 and 2K. ... product info for 2000. ... I am in the process of replacing it ...
    (microsoft.public.sqlserver.security)