Migrating SQL Server 2000 Logins

Mar 27, 2004

I'm changing servers and want to copy all the logins from the old server to the new server. Is there anyway to do this?

View 5 Replies


ADVERTISEMENT

Regarding Migrating Windows And SQL Logins To SQL 2005 From SQL 2000

Jul 27, 2006

Hey. I've a script which gets the SQL usernames with the information I need. Is it possible to migrate the passwords also with this information?

Also, regarding Windows Logins, do i have to worry about their SIDS when migrating to SQL 2005. I'm going to attach SQL 2000 db's onto a 2005SQL instance and these db's alreayd have the usernames assigned in them. Please let me know if there is a way out for the above two questions. thank you.

SELECT 'Create LOGIN [' + loginname + '] with password = ''hello'', sid = ',sid,
', default_database = ' + dbname + ', default_language = ' + language + ',check_expiration=off,check_policy=off'
FROM master..syslogins
WHERE name NOT IN ('sa')
AND isntname = 0

View 6 Replies View Related

Migrating SQL Server Logins/permissions

Apr 12, 2000

I need to move several databases to a new server while retaining the same logins/permissions. Books Online indicates that DTS can move the SQL Server logins, but it sets the passwords to NULL in the process. Is there any way to move the logins and keep all passwords/permissions intact?

View 2 Replies View Related

DB Engine :: Migrating Logins Related To Specific Database Not Whole Server Level?

Aug 25, 2015

<g class="gr_ gr_78 gr-alert gr_gramm Punctuation replaceWithoutSep" data-gr-id="78" id="78">Friends,</g>
<g class="gr_ gr_78 gr-alert gr_gramm Punctuation replaceWithoutSep" data-gr-id="78" id="78">I</g>

i am migrating one database from SQL Server 2008 where I have around 20 databases to SQLServer 2012. To migrate the login I was thinking about to use SP_Help <g class="gr_ gr_114 gr-alert gr_spell ContextualSpelling ins-del multiReplace" data-gr-id="114" id="114">revlogin</g> store procedure but now what I believe is this SP scripts out whole server level login and I don't need all the logins in the server except related to the database that I am migrating to.

<g class="gr_ gr_418 gr-alert gr_gramm Grammar multiReplace" data-gr-id="418" id="418">please</g>

best way to migrate logins only related to the specific database to the new server. 

View 4 Replies View Related

Migrating Sql Logins

Jun 26, 2003

We have a "spanking new" machine to run SQL server and moving the databases over was absolutely no problem.

However, we discovered that we left the user ids and passwords behind.

Is there a way to get them copied from the old database to the new one?

View 7 Replies View Related

Migrating Logins To Another

Oct 6, 2004

When using the script to transfer logins and passwords from one server to another. After doing so... Does the logins and passwords still appear on the server transfering from??? I am doing a parallel install and need to keep the production database logins and passwords still intact. Thanks...

I did a detach on each database/logs.
Moved to the exact location on the new server.

View 4 Replies View Related

Migrating SQL Logins With Password

Feb 6, 2007

HiI need to move a couple of SQL logins to a new machine to support a3rd party application. Problem is the password is embedded in theapplication and we can't see how to change it. Does anyone have amechanism for moving a login to a new machine *without* knowing orchanging the password?TIAChloe

View 1 Replies View Related

Problem With NT Authenticated Logins After Migrating To AD!!!!!!!

Sep 16, 2004

I have a developer who created a DTS package using an NT authenticated ID. Now that we've migrated the SQL Server to another Domain in Active Directory, I am showing the following error for his jobs:

"The job failed. Unable to determine if the owner (DomainUSer) of job EmployeeDump has server access (reason: Could not obtain information about Windows NT group/user 'DomainUSer'. [SQLSTATE 42000] (Error 8198)).

When I went to check and see what the permissions problem might be, I noticed that all of my NT Authenticated ID are broken after migration - in other words, I can add the Active Directory NT ID's to the SQL Server instance, but I cannot give these ID's permissions to databases because it says they already exist??? I know if I have a sql login that is 'orphaned', I can use "sp_change_users_login" to fix it, but I think I read that this won't work for NT authenticated IDs.

IS there a way to fix this short of dropping ALL of my NT authenticated logins and recreating them????????

View 3 Replies View Related

Migrating From Access 2000 To SQl Server 2000

Jul 20, 2005

Hi,I have developed an application using VB 6 (SP 5), MS Access 2000 andCrystal Reports 9. I migrated from from access to SQl Server 2000.This wasn't a problem as i could import all the tables to SQL Server.Also, i could make VB6 talk to SQl Server.The problem arsies when i run my application. The sql syntax foraccess seems to be different than that for SQL Server. A simpleexample being: In access boolean datatype is true/false ,whereas inSQL Server the boolean equivalent is bit (numerical 1 or 0). Thesekind of issues are causing problems and most queries don't run.Would i need to go and change all the queries in accordance with SQlServer syntax ,which would be very time consuming or is there anyfunction which will convert the access datatype into its equivalentSQl Server datatype??Any input/thoughts/suggestions would be appreciated.ThanksJatin

View 1 Replies View Related

Migrating Acceess To Sql Server 2000

Oct 3, 2002

Any suggestions on migrating Access97 tables to sql server 2000? The DTS seems cumbersome and the Access97 upsizing wizard add-in is only compatible up to sql server 7.0.

Thanks

View 1 Replies View Related

Migrating Sybase To SQL Server 2000

Feb 25, 2008

Hi all

I try to migrate sybase to SQL Server 2000, but found a los of trouble, please, some can help me to resolve this???

May many of that are easy to resolv, but is mi fist time with SQL Server 2000... plz, help :(

Object : Procedure
Error : Sintaxis incorrecta cerca de la palabra clave 'cursor'.
Code :

Create Procedure ABA_CenResul
as
Begin
declare @EST_CEN_Codigo char(8),
@EST_CEN_Descripcio char(100),
@n char(100),
@name char(100),
@salida char(8),
@vble int,
@ini int,
@ter int,
@indice int,
@aux_descripcion char(100)
declare sonido cursor
for
select EST_CEN_Codigo, EST_CEN_Descripcio
from EST_CenResul
open sonido
fetch sonido into @EST_CEN_Codigo,@EST_CEN_Descripcio
select @EST_CEN_Descripcio = @EST_CEN_Descripcio + " "
select @aux_descripcion = @EST_CEN_Descripcio
while @@sqlstatus !=2
begin
select @indice = 1
while @indice <> 4
begin
select @vble = patindex("% %",@EST_CEN_Descripcio)
select @ter = @vble - 1
select @name = substring(@EST_CEN_Descripcio,1,@ter)
if @indice = 1
select @n = @name
else
select @n = @n + "/" + @name

select @ini = @vble + 1
select @EST_CEN_Descripcio = substring(@EST_CEN_Descripcio,@ini,100)
select @indice = @indice + 1
end
print @n
exec sdxsrvr...soundex @n, @salida out
update EST_CenResul
set EST_CEN_Soundex = @salida
where EST_CEN_Codigo = @EST_CEN_Codigo
fetch sonido into @EST_CEN_Codigo, @EST_CEN_Descripcio
-- select @EST_CEN_Descripcio = @EST_CEN_Descripcio + " "
-- select @aux_descripcion = @EST_CEN_Descripcio
end
close sonido
deallocate cursor sonido
end



Thnx in advance

View 2 Replies View Related

Migrating From Oracle 8i To SQL Server 2000

Jan 31, 2004

Hi
I am trying to migrate my database in Oracle 8i to Sql Server 2000 but am unsure of how to carry out the migration. How do I do it and what do I have to consider. My OS is Windows 2003. Thanks in advance

View 2 Replies View Related

Migrating 2000 To 2005 On Same Server

Apr 2, 2008

Has anyone had experience of migrating from 2000 to 2005 on the same box , and maintaining the SERVERNAMEINSTANCE_NAME.
What are some effective ways of migrating and retaining the same servername/instance name ?

The issue revolves around minimising the use of extra boxes , as I would like to do the migration on the same server and keep the name the same .

Jack Vamvas
--------------------
Search IT jobs from multiple sources- http://www.ITjobfeed.com

View 3 Replies View Related

Migrating Access To SQL 2000 Server

Apr 25, 2007

Hi,

I need to migrate my access database to SQL2000 Server. I have three tables in my access database. In each table have 3000-6000 records.
So how to put all these records in to sql2000 server tables.
The table structure in Access database and sql2000 database are same.

Here core work is just insert all these 3000 - 6000 records (rows) from Access database to sql2000 database

Thanks in Advance!!

With regards
Shaji

View 5 Replies View Related

Migrating From Sql Server 2000 To 2005

Sep 28, 2007



Hi,

We are migrating from SQL Server 2000 to 2005. We currently use ADO.Net to make connection to sql server. I just want to know after migration to sql server 2005 do we have to make any changes in code in the way we make connection to use ADO.Net2 which is part of sql server 2005. ??


Thanks
Arvind

View 1 Replies View Related

Migrating SQL EXPRESS In SQL 2000 Or 2005 Server

Mar 26, 2007

whenever i modified the connection of my current database...I'll always got an error,when asking for "server name"..it says [DBNETLIB...etc]Named Pipes etc error..my current database was SQLEXPRESS and i want to change it as an SQL OLEDB,2000,2005.. but as i said il always got an error..sometimes it says "SQL server does not exit..ODBC" etc...when im entering the "server name"..so i could only used Access or SQLEXPRESS server database.. what should i do with the error?? thanks for helping again..   

View 6 Replies View Related

Migrating Sybase Databases To SQL Server 2000

Apr 27, 2004

Just a quick question, does anyone know any major issues with Migrating Sybase Databases to SQL Server? Just wondering if their any oddities I should be aware of? Thanks nixies

View 2 Replies View Related

ASP.NET Application - Migrating From Access 2000 To SQL Server 7

Jul 23, 2005

First off, sorry if my cross posting offends anyone. I'm posting thisin Access and SQL Server groups - not sure which one is appropriate.I have a relatively simple ASP.NET/VB.NET application that is nowhitting an Access 2000 database over an intranet. We have to migratethe database to SQL Server 7. My experience with ASP.NET is prettylimited and my experience with SQL Server is nonexistent.We have an MSDN subscription, so I went to the downloads section to getSQL Server 7. Guess what? SQL Server 6.5 is available, as is 2000 and2005, but no SQL Server 7. So my first question is, does anyone know ifit is available for MSDN subscribers?The next question is, does anyone know of a good resource that explainshow to make the transition from Access 2000 to SQL Server 7? I know thedata has to be migrated and the connection between the application andthe database modified, but am really not sure exactly what to first andthe correct way to go about it. The application is a simple productconfigurator. There's not a lot of data and it's not a very complexdatabase.Thanks in advance. If you'd like, please copy responses tolcifers(AT)yahoo.com (AT) = @TIA.Cheers.- Luther

View 2 Replies View Related

Transfer Logins From SQL Server 2000 To 2005

May 13, 2008

Hi

How to transfer logins from 2000 to 2005?


Raj.

View 1 Replies View Related

Migrating Large Amounts Of Data From SQL Server 7.0 To 2000

Jul 20, 2005

I'm in the process of migrating a lot of data (millions of rows, 4GB+of data) from an older SQL Server 7.0 database to a new SQL Server2000 machine.Time is not of the essence; my main concern during the migration isthat when I copy in the new data, the new database isn't paralyzed bythe amount of bulk copying being one. For this reason, I'm splittingthe data into one-month chunks (the data's all timestamped and goesback about 3 years), exporting as CSV, compressing the files, and thenimporting them on the target server. The reason I'm using CSV isbecause we may want to also copy this data to other non-SQL Serversystems later, and CSV is pretty universal. I'm also copying in thisformat because the target server is remotely hosted and is notaccessible by any method except FTP and Remote Desktop -- nodatabase-to-database copying allowed for security reasons.My questions:1) Given all of this, what would be the least intrusive way to copyover all this data? The target server has to remain running and berelatively uninterrupted. One of the issues that goes hand-in-handwith this is indexes: should I copy over all the data first and thencreate indexes, or allow SQL Server to rebuild indexes as I go?2) Another option is to make a SQL Server backup of the database fromthe old server, upload it, mount it, and then copy over the data. I'mworried that this would slow operations down to a crawl, though, whichis why I'm taking the piecemeal approach.Comments, suggestions, raw fish?

View 2 Replies View Related

Problem Occurs When Migrating A SQL Server 2000 Database To A SQL Server 2005 Server

Sep 20, 2006

When I try to migrate a database on a SQL Server 2000 server to a SQL Server 2005 server with the Copy Database Wizard of the SQL Server Management Studio, I'm confronted with the following problem;

Performing operation...

- Add log for package (Success)
- Add task for transferring database objects (Success)
- Create package (Success)
- Start SQL Server Agent Job (Success)
- Execute SQL Server Agent Job (Error)
Messages
* The job failed. Check the event log on the destination server for details. (Copy Database Wizard)

When I take a look at 'Event viewer' on the SQL 2005 server, the following error is displayed;

InnerException-->An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005,
this failure may be caused by the fact
that under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

I already enabled the MSSQLSERVER network configuration protocols (TCP/IP and Named Pipes ).

How do I solve this problem?





View 9 Replies View Related

SQL Server 2000: Tracking Down Source Of Failed Logins

Oct 4, 2006

I was checking the logs because of some failing backups and found literally hundreds of enties for failed logins for user sa. This is does not seem to be related to the failed backups, because even after fixing the problem (disk space), the entries continue to pile up.

Needless to say, the information provided in the log is a bit sparse: date and time, source (Login), message (Login failed for user 'sa'.). If that is actually enough to go on, then there must be some way of cross-referencing this information with that found somewhere else. Is there a 'somewhere else' or are there other things I need to do in order to track this down?

I don't suspect any malicious intent, but I'm not ruling it out. My main concern at this point is twofold: to gain a better understanding of system management; to identify and correct the failed login.

Any recommendations, whether tools, documentation, or otherwise are very much appreciated.

Ron.

View 1 Replies View Related

Migrating Reporting Services From SQL Server 2000 To SQL Server 2005

Mar 31, 2008



Hi,

I'm migrating SQl Server Reporting Services from 2000 to 2005.The reports are generated normally in 2000 but it seems that it is taking more time in 2005 or sometimes it does not generate the report at all.Could you kindly suggest a solution?

Thanks,
anne

View 1 Replies View Related

Migrating MS-SQL Server 2000 To MS-SQL Server 2005 For Web Application On .Net Framework 1.1

Aug 10, 2006

Hello,

I have to do an impact analysis for migrating a .Net web based application. The current and desired scenarios are mentioned below.

The current environment:

OS - Windows 2000, SP4

Framework - .Net 1.1

SQL Server - MSSQL Server 2000

Desired Environment:

OS - Windows 2003, SP1 / Windows 2003 R2

Framework - .Net 1.1

SQL Server - MSSQL Server 2005

Please let me know

1. If any changes need to be done in the application when migrating the database from 2000 to 2005?

2. Any relevant document which will help me in the same.

Regards, Venkat





View 1 Replies View Related

Migrating SQL Server 2000 Stored Procedures To SQL Server 2005

Dec 20, 2007

I have successfully moved my data from a SQL Server 2000 hosting site to a SQL Server 2005 hosting site. I Made a backup of my database using Enterprise Manager (2000) and imported the database tables using SQL Server Management Studio (2005). I do not know how to move the 25 or so stored procedures that I have in SQL Server 2000. I have a very short amount of time to figure this out and am hoping that someone can give me a brief step by step answer on how to get this done. I would appreciate any information you can provide. Thank you!!

View 5 Replies View Related

SQL Server 2000 To 2005 Upgrade (Database Users Logins)

Jul 6, 2007

Hi All,

I have just migrated couple of test databases

from SQL Server 2000 to 2005 (side by side).



I also migrated the server level logins using SSIS transfer logins task, available on SSIS 'Transfer logins', I selected all the databases that I have migrated so that I have all database users account in server logins (to avoid orphaned users); but I don't have all the database users in server logins, also the sys.sysusers doesn't have the database users, that I have moved to SQL 2005. Can anybody help?



Also do I need to back up the SQL Server 2000 database and restore it on SQL 2005? What impact this operation can have?



Thanks for your time..



Bidyut



View 5 Replies View Related

Problem Migrating From Sql Server 2005 To Sql Server 2000

Dec 9, 2007

HI,

i have tried the below three steps but i dont get script to any output file or clipboard after the executing the script generation. And i would also like to why i get lo of errors when i run the scritp from the step one,i got the script and i try to run it on sql server 2000,there is lot of errors. I there any order i need to follow when i run the script in sql server 2000.

Plz help me out. This is urgent.....

How to Downgrade a Database from SQL Server 2005 to SQL Server 2000

As you may all know, SQL Server 2005 request a minimum of 8GB RAM to work€¦ let say satisfactorily. I first didn€™t knew that and after a while from the upgrade I did from SQL Server 2000 to 2005 my SQL Services were starting to crash three or four times per DAY!!!

At first I thought I was being attacked, but soon I realized it was nothing like that. I then decided to downgrade to an SQL Server 2000 edition. Though I looked around the internet to find some information on how to do that, I got very disappointed when I realized that no actual documentation of any kind could be found for that. So I am posting this thread to inform you on the procedures I had to follow for this action.

Before beginning I must assume, firstly that the user, who will attempt such thing, has a basic knowledge of SQL Environment, secondly that he has the two versions already installed (both 2000 and 2005), that a basic backup of the databases has been created and finally that all the 2005 SQL Server Users have been created at the SQL Server 2000 environment as well.

Step 1 Generating Scripts for the Database Elements and Structures

1) Right-click over the desired Database at 2005, Choose Tasks and the Generate Scripts (Option).
2) At the pop-up Dialog Box click at the Script All Objects in the selected Databases check box, to activate it and then Click the Next Button.
3) Set the following Elements to the following Values
a. Script Collation , set to TRUE
b. Script Database Create, set to TRUE
c. Script of SQL Version, set to SQL SERVER 2000
d. Script foreign keys, set to FALSE
e. Script Triggers, set to FALSE
Then Hit the Next button
4) Select the way the generated scripts should be saved (There are different selections. The most common one is Clipboard). Finally click the Next button till you reach the end.
5) Click Finish

After completing this procedure, we have to move to the SQL SERVER 2000 environment. Here, by using the Query Analyzer, we will have to run the scripts that were generated using the master database. Copy and Paste the script at the Query Analyzer and run it. After that the Structure of the Database will be created.

Be careful, the SQL Server 2005 Edition inserts the Views in a random place through the script. Therefore, all the scripts that are referred to the Views MUST be moved to the end of the script. If the Query Analyzer shows some errors do not be bothered. Delete all the elements created from the script and after you fix the code run it again.


Step2 Moving the data from 2005 to 2000

1) After completing the previous step successfully, moving the data follows. Right-click at the 2005 database you used to run the previous step and select Tasks and then choose the Export Data (option).
2) From the pop-up Dialog Box, select the Source Db and Click at the Next Button.
3) At the next step you will have to choose the destination server and the destination Database for the Data to be exported. Then Click Next.
4) A List of all the Source Database€™s Elements will appear in the screen. Select one by one all the Elements you wish to move and for each one click at the button Edit Mappings (Located at the bottom right corner of the Dialog Box just under the Elements list). A new Dialog box will pop-up. Select the Delete rows in Destination Tables option and activate the Enable Identity Insert Option. (Remember to repeat this action for each of the selected Element from the list that will be moved.

CAUTION!!! A malfunction of the SQL Server 2005 has been found. Not sure why, after multiple tries I have observed that when I tried to move more than twelve Elements at once, the Export Data Wizard of SQL Server 2005 seemed to disable the Enable Identity Insert Option that was activated over the Edit Mappings Dialog Box. But if the number of the selected Elements is smaller than 12 no problem seemed to appear.

Step 3 Generating Scripts for the Database Foreign Keys and Triggers

Finally, to successfully finish the downgrade of the Database, the Triggers and the Foreign Keys of the DB must be produced. The procedure that should be followed is the one stated next:

1) Right-Click at the SQL 2005 Database and Select from Tasks Menu the Generate Scripts Option.
2) Using the pop-up Dialog Box make sure that the check box Script All Objects in the selected Databases is not enabled and hit the Next Button.
3) Set all the Elements on the List to a False Value except the ones that follow:
a. Include IF NOT EXISTS , set to TRUE
b. Script Owner, set to TRUE
c. Script of SQL Version, set to SQL SERVER 2000
d. Script foreign keys, set to TRUE
e. Script Triggers, set to TRUE
Then Hit the Next button
4) After finishing reading the Elements of the Database, a new list will appear at the Dialog Box. Make sure that you select ONLY THE TABLES of the Database and hit the Next Button.
5) At the screen that follows hit the Select All button and the Next.
6) Select the way the generated scripts should be saved (There are different selections. The most common one is Clipboard). Finally click the Next button till you reach the end.
7) Click Finish Button.

After completing this procedure, we have to move to the SQL SERVER 2000 environment. Here, by using the Query Analyzer, we will have to run the scripts that were generated using the master database. Copy and Paste the script at the Query Analyzer and run it. After that the Foreign Keys and the Triggers of the Database will be created.

After these steps the database should be fully functional under the SQL Server 2000 edition.

View 1 Replies View Related

Move Logins From A Sql 2000 Server To A Sql 2005 Server

Dec 4, 2006

Hi guys,
I have tried to use the sp_help_revlogin script to move logins from a sql 2000 server to a sql 2005 server. It works for users that have a password. But if the password is blank it will fail. Is there a work around for this since I can't change the users passwords?
I have also tried SSIS package but that too doesn't work because of the same reason.

Can anyone help...

View 1 Replies View Related

Problem Migrating Application Database From SQL Server 2000 To Express Edition 2005

Jan 21, 2008

Hi there

I am new to SQL Server, but the current project that I am working on has the following requirement:-

1) Migrate the application (a servlet based web application on Apache Tomcat) from Solaris to Wintel
2) Migrate the supporting database from SQL Server 2000 to Sql Server 2005
3) Get IIS to communicate with Tomcat for serving servlet/jsp etc to the client

Though I successfully completed item 1 above, am stuck at item 2. Details are below

Actions taken for item 2

A. Installed MS 2005
B. Created new database in MS 2005 (logged in as user 'sa')
C. Generated SQL scripts (such as create table table_A etc) from existing MS 2000
D. Genearted SQL scripts (such as insert into table_A etc) from existing MS 2000
E. Created new schema in MS 2005
F. Ran scripts C & D in the new schema. All tables are records populated.
G. Obtained new JDBC driver and test run to see if connection is working fine, and it worked. Even ran an sql statment


Code Block[select count(*) from sa.table_A]

and got appropriate response.


H. When I made the application to talk to this new database (which is a copy of Production from step C, D above), it's behaving as though it cannot find the record.
I. When I further debugged, I realised that the web application is excuting queries without mentioning the schema. For eg.



Code Block[Select firstName, lastName from table_A]

Or rather it assumes that the user connecting to database is same as the schema name.


J. To further ascertain my point, I ran the query


Code Block[Select firstName, lastName from sa.table_A]

and it worked!



Now the real problem is that I cannot modify the existing code to append a schema name and this approach is rather not recommended best practise.


I tried to match the user name with the schema name, even made this schema as default to the user. But still not finding any luck.

I request all you experts out there to help me out with this problem.

Regards,

prad.nair

View 3 Replies View Related

Migrating From SQL Server 2000 To SQL Server 2005

Jan 22, 2008

Hi All,

We are planning to migrate from SQL Server 2000 to SQL Server 2005.

I am trying to connect to the SQL Server 2000 using SQL Upgrade Advisor. But I am getting the following error whenever I click on the detect button after entering the server name:


Upgrade Advisor could not detect SQL Server component on the server.

The Network Path was not found.(mscorlib)

Please let me know if any of you have faced the same issue.

Thanks,

Suhas

View 3 Replies View Related

Migrating From SQL Server 2005 To SQL Server 2000

Jul 3, 2006

I have to 2 database server, one is running in SQL Server 2005 and the other one is SQL Server 2000. Now, I want to transfer my database from SQL Server 2005 to SQL SERVER 2000 and gives error. Any solution?

Thanks

Ronie

View 1 Replies View Related

Export Logins To Server With Already Existing Logins

Jul 17, 2001

Hello,

I would move a Database to another server. I try to use DTS but I have problems with this process because DB have big tables, I think. I try to use DETACH and ATTACH procedures but logins doesn't export. And more, in new server there are already logins from another DBs.

What's the best way to solve this problem?
Please, help
Thanks

View 3 Replies View Related

Moving DBs From SQL Server Logins To Windows Logins

Apr 3, 2007

I am a systems analyst and work with an app that runs against 2 SQL Server DBs. Though I have some familiarity with SQL Server and SQL, I am not a DBA.

The app executable is tied to a Windows service.
When we install the app, we run a process that builds 2 dbs to include:
Tables, indexes, stored procedures, views and user accounts.
SQL Server is set up for mixed mode authentication.

Normally, the dbs run off the local db user accounts which are tied to local logins with the same names.
We have a client that wants to remove our standard logins so that they can run on only a Windows login.
I know I should be able to tie the db users to a Windows login.
And I can do the same for the service.

But I am at a loss as to how to get this done.
How do you associate db users with a Windows login?
When I have tried sp_change_users_login I get an error that the Windows login does not exist. (Though I have added the Windows account to the DB.)

Hope this all makes sense.

View 2 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved