@cirquedeSQL

When I ran that script, out of 300 orphaned users around 250 got syncronized.

I came to know about the 50 by running the--

exec sp_change_users_login 'REPORT'

When I tried to syncronize those...

India --> chicago

chicago --> British virgin islands

British virgin islands--> ??

@cirqued

Did you restore this database to a different server?

There are scripts here at SSC and on the web that will help you fix all users at once.

Here is one such...

@ssismaddy

I think that did the trick...

but when I executed

Exec sp_change_users_login 'REPORT'

to see which all other users became orphan, there were 300 more...:(

so.. Is there a way...

Does this only happen for one specific user?

This appears to be happening in an application. Have you verified the connection string to be correct?

What is the default database for the...

yes, these things happen sometimes, i guess bug in sql2k5 maintenance plans..

@ cirqued

The logins disabled are the users...For ex bre,gra,jon etc..

I asked, nobody did it..

Now can i enable all at 1 script or each one of them differently from GUI.

Which logins were disabled? Ones that you created?

Are you creating these via script or through the gui?

The server level logins...I didnt create them.

They were made when the server was...

@ lowell

got it....

thanks a lot

Sushant

Virgin Islands

@ lowell

So the synonyms A,B and C which i created will be local to database level or server level..?

and how to deallocate those synonyms once the use is over?

thanks

Sushant

Virgin Islands

@ lowell

thanks it worked...

no im not logging into xyz server..

im using it as a linked server as my query takes output from 2 servers..

is there a way?

@sumanth

wat version of sql server are you using..

backward compatiblity in restoring a databse is not there

make sure.

Sushant

@ sushant

It's not considered good practice to shrink a production database.

If the database has been shrunk and new data is added then it has to grow again, probably at...