Re: authentication on SQL 2005

No error other than invalid user name and password.

Yes the password is valid, I use it to connect with the SQL Server
Management Studio using SQL Server Authentication and the SA is set with
server role "sysadmin"

I am just wondering if there is something in SQL 2000 that is automatically
on that is not turned on in SQL 2005 for this authentication to take place.

"PSPDBA" <williambr@xxxxxxxxxxx> wrote in message
news:1147285864.526093.215500@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Are you getting an error back? Did you set an SA password when you
installed SQL2k5?



.

Relevant Pages

  • Programmatically create DSN usind SQL Server Authentication
    ... I am trying to programmatically create a DSN on a target system for SQL ... Server using SQL Server Authentication. ... is off-topic for my purpose because it only shows Windows authentication. ...
    (microsoft.public.sqlserver.odbc)
  • Re: Connexion to SSIS
    ... A way to verify it the account in question to the local admins and try ... If you do not want to, can use proxy accounts. ... only SQL Server authentication and use it to connect my remote client to the ... SQLServer Account by SQL Server Authentication? ...
    (microsoft.public.sqlserver.dts)
  • How to disable the Windows NT login authenticate at SQL-Server 2000 login Form ? @Thanks
    ... Use Ms SQL Server 2000, There are two way to login, The first is Windows NT ... Authentication, The second is SQL Server Authentication, If you choose ... I think the Database ...
    (microsoft.public.sqlserver.security)
  • Re: Programmatically create DSN usind SQL Server Authentication
    ... Not when you create the DSN programmatically. ... >Server using SQL Server Authentication. ... >is off-topic for my purpose because it only shows Windows authentication. ...
    (microsoft.public.sqlserver.odbc)
  • Re: Failed to login with sa
    ... > and forth between Windows Authentication and SQL Server Authentication, ... > I can't login with sa account. ... In order to login as 'sa', you need to use SQL Server Authentication. ...
    (microsoft.public.sqlserver.security)