Re: Sql Server 2005 Dev. Ed. on Windows Server 2003

Check out this KB which is about transferring Logins: http://support.microsoft.com/kb/246133

--
Ekrem Önsoy



"BrianR" <BrianR@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:DDCBC96A-6865-4B41-BC8F-BAFBA1281C5D@xxxxxxxxxxxxxxxx
Thanks Ekrem. I think I'm getting closer. I've never transfered just logins.
Can you provide the steps?

Also, since this is running on a newly installed Windows Server 2003, is
there anything I need to do on the windows server side as far as logins?

BrianR

"Ekrem Önsoy" wrote:

Hi Brian,

Detach\Attach or Backup\Restore only works at database level. Logins are
server level objects. So, you should also create your Logins or transfer
them from your older SQL Server instance to the newer one.

--
Ekrem Önsoy




"BrianR" <BrianR@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2571066A-25E8-4316-AF68-263F5A49FB33@xxxxxxxxxxxxxxxx
>I am able to login to the SQL 2005 database using the "sa" login from >ODBC
>on
> another computer but I can't login with the database UID/PW from ODBC > on
> the
> other computer. All I did was detach from a SQL 2000 computer, copy the
> database over and attached it to the SQL 2005 computer. I assumed the
> database logins came over with the attach(ment). Why would it not > accept
> the
> same UID and PW on the SQL 2005 computer?
>
> BrianR
>
> "Ekrem Önsoy" wrote:
>
>> First of all, it seems that you are attempting using SQL Server 2005
>> Developer Edition for your production server. This is against the >> license
>> agreement of this product of Microsoft. You are allowed to use this
>> edition
>> of SQL Server only for demonstration, test and development purposes >> and
>> of
>> course if you have a valid license for it.
>>
>> You did not mention if your Windows XP is with its SP2 or not, but
>> Windows
>> Server 2003 has a Windows Firewall ships with it. And this Windows
>> Firewall
>> comes also with Windows XP' s SP2. Have you configured your Windows
>> Firewall
>> on your Windows Server? For Windows Firewall settings see these links:
>> http://support.microsoft.com/kb/841249
>> http://msdn.microsoft.com/en-us/library/ms175043(SQL.90).aspx
>>
>> I suggest you to try to connect to your SQL Server instance on the
>> Windows
>> Server machine using SSMS which is installed on your Windows XP >> machine.
>> So,
>> you'll see if the problem is about the software settings or if there >> is
>> another problem (with the Windows Firewall, or port, or protocol
>> configuration) or your Windows Server or SQL Server...
>>
>> -- >> Ekrem Önsoy
>>
>>
>>
>> "BrianR" <BrianR@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:CC3DFD49-2D92-47DE-9441-6AFD17C1C31B@xxxxxxxxxxxxxxxx
>> > I'm replacing an older computer which is running Widows XP Pro and >> > Sql
>> > 2000.
>> > We are accessing the current sql server via a web app (ASP). This >> > has
>> > worked
>> > great but it's time to upgrade and I've purchased a new Dell server
>> > with
>> > Windows 2003 Server installed. I've done the following:
>> > - installed SQL 2005 Dev. Ed.
>> > - made sure sql server was set to allow remote connections (Sql >> > Serv.
>> > Config)
>> > - created a new DSN on the web server to point to new sql server
>> > - attached database(s) after detaching the database(s) on the old >> > sql
>> > server 2000 and copying the MDF/LDF files over to the new sql server
>> > 2005
>> >
>> > I continue to get 500.100 error (ADODB.Recordset (0x800A0E78)
>> > "Operation
>> > is
>> > not allowed when the object is closed". This is failing in the
>> > index.asp
>> > file
>> > as soon as it tries to read a recordset from the database. It >> > doesn't
>> > complain when it connects to the database using DSN.
>> >
>> > I installed SQL 2005 Dev. Ed. on my laptop (XP) with IIS running and
>> > I've
>> > been able to connect to my local DB using DSN and on the older Sql >> > 2000
>> > server using DSN without an issue.
>> >
>> > What is so different with SQL Server 2005 on XP Pro and Server 2003?
>> >
>> > BrianR
>>
>>


.

Relevant Pages

  • Re: SQL Server 2005 Login Problem
    ... There are two authentication method in SQL Server. ... 1- Windows Authentication ... 2- Mixed Authentication (through SQL Server logins and Windows accounts) ...
    (microsoft.public.sqlserver.clients)
  • Re: New Windows Infrastructure
    ... vendor's application runs on windows with an SQL database and I will also need a web server for a separate module which will allow our customers to access account data online. ... I would think that if the app runs on windows, I do not need the citrix server. ... It makes sense to have separate DCs though, because let's say you want to upgrade your Active Directory in two weeks time, with separate DCs it's easy, but if you've got a bunch of apps installed it could be a nightmare. ...
    (microsoft.public.win2000.setup_deployment)
  • How can I avoid using SQL Authentication with the Office Web Parts?
    ... We have a machine running Windows 2003 Server, IIS 6, and Windows SharePoint ... We are using Office Web Parts on several Web ... Part pages to display data retrieved from a SQL Server (SQL 2000 SP3 running ...
    (microsoft.public.office.developer.web.components)
  • How can I avoid using SQL Authentication with the Office Web Parts?
    ... We have a machine running Windows 2003 Server, IIS 6, and Windows SharePoint ... We are using Office Web Parts on several Web ... Part pages to display data retrieved from a SQL Server (SQL 2000 SP3 running ...
    (microsoft.public.inetserver.iis)
  • How can I avoid using SQL Authentication with the Office Web Parts?
    ... We have a machine running Windows 2003 Server, IIS 6, and Windows SharePoint ... We are using Office Web Parts on several Web ... Part pages to display data retrieved from a SQL Server (SQL 2000 SP3 running ...
    (microsoft.public.sharepoint.windowsservices)