Cannot Authenticate User to Database SQL SERVER 2005

Hello Experts,

I have a SQL Sserver 2005 Database that was created on another system... It is authenticating with the sa password.

When I attach the databse to the new SQL Server, My application (accessing the DB with OleDB SQL Native Client) cannot log onto the SQL Server databse.

When I go to sa properties,  and the User Mapping page, I am unable to map to the desired database. If I create a new database I can map to it. This feels like a SID issue.

Does anyone know how to get around this??

Thanks!
SaxitalisAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
SaxitalisConnect With a Mentor Author Commented:
I think this was a SID issue due to a DB created on one system and copied over to anotner system - thanks for your comments though!
0
 
rob_farleyCommented:
Actually, it sounds like you might be in Windows Authentication Only mode. Go to the Security page of the Server properties (instance properties of SQL, in SSMS), and make sure that "SQL Server and Windows Authentication mode" is selected.

Hope this helps. :)

Rob
0
 
SaxitalisAuthor Commented:
I am definitely in Mixed mode.

Like I mentioned, I can map any user (includingsa) to a new database of the same name but cannot map to this existing datbase.

It feels like something with the old database that is preventing this from happening. Could it be a SID problem??

Thanks
0
[Webinar] Improve your customer journey

A positive customer journey is important in attracting and retaining business. To improve this experience, you can use Google Maps APIs to increase checkout conversions, boost user engagement, and optimize order fulfillment. Learn how in this webinar presented by Dito.

 
rob_farleyCommented:
Yeah, ok... could be a SID thing then. Annoyingly, you can't remove 'dbo', which is the user that maps to 'sa'.

Umm.... let me think and get back to you.

Rob
0
 
Jagdish DevakuSr DB ArchitectCommented:
Hi,

Try the following...

1. Go to the security folder of the <attached database> and delete all the users in that folder.

2. Now restart the sql services

And try to access the database using sa user...

If its still giving error check the roles under security under <attached database> and delete user defined roles in database roles as well as application roles.

and this might work...

let me know if you face any issues...

all the best...
0
 
rob_farleyCommented:
Is your application accessing the system as sa?
0
 
Jagdish DevakuSr DB ArchitectCommented:
and check compatibility level of the database you attached. if it is not set to 90 then change it to 90 and restart the server.
0
 
storysoftCommented:
Try this:
--Add the new login.
USE master
go
EXEC sp_addlogin '[login name]','[password]','[default db]'
go

--Change the user account to link with your login.
USE [your database name here]
go
EXEC sp_change_users_login 'Update_One', '[login name]', '[user in db you want to map to]'
0
 
Jagdish DevakuSr DB ArchitectCommented:
Try the following...

select @@SERVERNAME

If this returns the same instance name you are using, then its OK...

otherwise change the instance to the current instance you are using...

To change the instance name run the following...

USE MASTER
GO
SP_DROPSERVER '<Old_Instance_name>'
GO
USE MASTER
GO
SP_ADDSERVER '<New_Instance_name>', 'LOCAL'
GO
0
All Courses

From novice to tech pro — start learning today.