New to MS SQL Server, Need help with Windows Authentication

I am new to the whole ASP .NET scene, so my knowledge is very limited, and if I’m not clear enough please let me know.

I am reading a book published by APress about ASP .NET with C# and I am at the point where I get to begin working with data (fun!!). The problem is that I’m not able to connect to the SQL Server. I have Server 2003 and SQL Server 2005 running on a separate machine than the computer that I use for development – the server is named THESERVER, the SQL server is named THESQLSERVER, and the computer I use for development is my laptop named MYLAPTOP.

So here’s my connection string (I put this in my web.config XML file):

<add name="Pubs" connectionString="DataSource=THESERVER\THESQLSERVER;
 Initial Catalog=pubs;Integrated Securit=SSPI"/> 

Now here’s what my book reads: For Windows authentication to work, the currently logged-on Windows user must have the required authorization to access the SQL database. This is all it says about Windows authentication because the book assumes that I am running MS SQL Express off localhost.

Questions:

Does the book mean that I will have to add a user to my server for my laptop? If so, how do I log into this user using the connection string?What does it mean by “the current logged-on Windows user”? Is that referring to the user on my laptop, or a user on the server?

I’ve been reading around trying to find more information on exactly how Windows authentication works, but I keep coming up dry. I know that much of this is probably trivial to a lot of you, which is why I am asking because it isn’t to me.

Well, thanks in advance for any help that you can provide me.

<add name="Pubs" connectionString="DataSource=192.168.1.56;
 userid=sa; password=mypassword"/> 

In the connecting string you need to specify an ip address a user name and password if the SQL

runs in another computer, if you got integrated windows authentication is another story, but I would try with SQL authentication

|||

Thanks for the response.

I know that I can do itthis way - using SQL authentication instead - but I was hoping thatthey may be some way of doing it through the Integrated WindowsAuthentication method. The only reason why I want to do it thisway is because of the claim that it is much more secure this way. If anyone can say otherwise and prove that it isn't that much moresecure, that is relatively the same, please tell me :D. That isthe only reason that is holding me back from using th SQLauthentication approach.

Thanks again for the quick response, I really appreciate it.

|||Anyone else with suggestions/solutions?|||Actually setting it to InProc, or ServerState is as secure as SQL Sessin State|||Setting which, MS SQL Server? How do I do that?

New Sysadmin cannot stop SQL instance...

Currently, I'm running SQL Server 2000 on Windows 2000
Advanced Server. I created a new Windows user who is not
in the Administrators group. Then, I entered into the SQL
instance's properties and changed the startup account to
be this new user's credentials. As a result, SQL created a
login for this new user and added him to the System
Administrators server role. When I log into the system as
this new user, I'm able to start the instance but I'm not
able to stop it. I don't understand this behavior since a
System administrator has SHUTDOWN privileges. Any
assistance is greatly appreciated.
Sincerely,
ABGYou will need to give the user rights to start/stop services.
Many dbas have administrative access on the windows boxes
used as sql servers.
"ABG" <abimael.garcia@.unisys.com> wrote in message
news:060501c34a59$86410a20$a101280a@.phx.gbl...
> Currently, I'm running SQL Server 2000 on Windows 2000
> Advanced Server. I created a new Windows user who is not
> in the Administrators group. Then, I entered into the SQL
> instance's properties and changed the startup account to
> be this new user's credentials. As a result, SQL created a
> login for this new user and added him to the System
> Administrators server role. When I log into the system as
> this new user, I'm able to start the instance but I'm not
> able to stop it. I don't understand this behavior since a
> System administrator has SHUTDOWN privileges. Any
> assistance is greatly appreciated.
> Sincerely,
> ABG
>|||Thank you for your response. I'm using Windows 2000
Advanced Server and I don't see the user right (start/stop
service). I do see (Logon as a service) and the user
already has that privilege. I purposely don't want to make
this user an administrator of the system but I do want him
to be able to shutdown the SQL Server instance. Do you
have any other suggestions?
>--Original Message--
>You will need to give the user rights to start/stop
services.
>Many dbas have administrative access on the windows boxes
>used as sql servers.
>"ABG" <abimael.garcia@.unisys.com> wrote in message
>news:060501c34a59$86410a20$a101280a@.phx.gbl...
>> Currently, I'm running SQL Server 2000 on Windows 2000
>> Advanced Server. I created a new Windows user who is not
>> in the Administrators group. Then, I entered into the
SQL
>> instance's properties and changed the startup account to
>> be this new user's credentials. As a result, SQL
created a
>> login for this new user and added him to the System
>> Administrators server role. When I log into the system
as
>> this new user, I'm able to start the instance but I'm
not
>> able to stop it. I don't understand this behavior since
a
>> System administrator has SHUTDOWN privileges. Any
>> assistance is greatly appreciated.
>> Sincerely,
>> ABG
>
>.
>|||Unfortunately I don't know what rights you need to assign, but
would question why you believe you cannot trust the person
responsible for corporate data with your network.
"ABG" <abimael.garcia@.unisys.com> wrote in message
news:017201c34bb9$248932b0$a301280a@.phx.gbl...
> Thank you for your response. I'm using Windows 2000
> Advanced Server and I don't see the user right (start/stop
> service). I do see (Logon as a service) and the user
> already has that privilege. I purposely don't want to make
> this user an administrator of the system but I do want him
> to be able to shutdown the SQL Server instance. Do you
> have any other suggestions?
>
>
>
> >--Original Message--
> >You will need to give the user rights to start/stop
> services.
> >
> >Many dbas have administrative access on the windows boxes
> >used as sql servers.
> >
> >"ABG" <abimael.garcia@.unisys.com> wrote in message
> >news:060501c34a59$86410a20$a101280a@.phx.gbl...
> >>
> >> Currently, I'm running SQL Server 2000 on Windows 2000
> >> Advanced Server. I created a new Windows user who is not
> >> in the Administrators group. Then, I entered into the
> SQL
> >> instance's properties and changed the startup account to
> >> be this new user's credentials. As a result, SQL
> created a
> >> login for this new user and added him to the System
> >> Administrators server role. When I log into the system
> as
> >> this new user, I'm able to start the instance but I'm
> not
> >> able to stop it. I don't understand this behavior since
> a
> >> System administrator has SHUTDOWN privileges. Any
> >> assistance is greatly appreciated.
> >> Sincerely,
> >> ABG
> >>
> >
> >
> >.
> >|||This is purely for testing and research purposes. I'm
trying to determine security best practices for multiple
SQL instance scenarios. In a SQL consolidation case,
politics becomes an issue: one department owns one
instance and another department may govern another. So,
internal security and isolated administration becomes an
issue. Basically, I was trying to setup a case where there
are completely separate sysadmins for each instance
inwhich they cannot affect the operations of the other
instances i.e. startup/shutdown the other instances.
I wanted a sysadmin of an instance to be able to
perform all tasks on his instance including
startup/shutdown. But I didn't want that sysadmin to have
full administrative rights on the whole system. Now it
appears that he must be an Administrator of the system in
order to do this. And this is very interesting because by
default the Builtin\Administrators windows group is added
to the System Administrators role. Therefore, if all
sysadmin users from all instances are also a part of the
Administrators windows group then they can essentially
perform administrative activities on the other instances.
And this is what I'm trying to prevent. Thank you for all
your help.
Sincerely,
ABG
>--Original Message--
>Unfortunately I don't know what rights you need to
assign, but
>would question why you believe you cannot trust the person
>responsible for corporate data with your network.
>"ABG" <abimael.garcia@.unisys.com> wrote in message
>news:017201c34bb9$248932b0$a301280a@.phx.gbl...
>> Thank you for your response. I'm using Windows 2000
>> Advanced Server and I don't see the user right
(start/stop
>> service). I do see (Logon as a service) and the user
>> already has that privilege. I purposely don't want to
make
>> this user an administrator of the system but I do want
him
>> to be able to shutdown the SQL Server instance. Do you
>> have any other suggestions?
>>
>>
>>
>> >--Original Message--
>> >You will need to give the user rights to start/stop
>> services.
>> >
>> >Many dbas have administrative access on the windows
boxes
>> >used as sql servers.
>> >
>> >"ABG" <abimael.garcia@.unisys.com> wrote in message
>> >news:060501c34a59$86410a20$a101280a@.phx.gbl...
>> >>
>> >> Currently, I'm running SQL Server 2000 on Windows
2000
>> >> Advanced Server. I created a new Windows user who is
not
>> >> in the Administrators group. Then, I entered into the
>> SQL
>> >> instance's properties and changed the startup
account to
>> >> be this new user's credentials. As a result, SQL
>> created a
>> >> login for this new user and added him to the System
>> >> Administrators server role. When I log into the
system
>> as
>> >> this new user, I'm able to start the instance but I'm
>> not
>> >> able to stop it. I don't understand this behavior
since
>> a
>> >> System administrator has SHUTDOWN privileges. Any
>> >> assistance is greatly appreciated.
>> >> Sincerely,
>> >> ABG
>> >>
>> >
>> >
>> >.
>> >
>
>.
>

New SQL server to replace old SQL server

Hi
We are getting ready to replace an old NT old SQL server with a New
Server, New Windows and SQL.
I would like to setup the new server with a new name for testing and
once we have it working rename it to the old server name. There are some
ODBC connections that use the name and I suspect a few other things
setup that way as well.
Does that cause an issue with SQL to rename a server?
Thanks
Will
Hi,
After testing you can rename the sql server with out any issues.
Use:-
SP_DROPserver <servernaem>
Go
SP_ADDSERVER <name>,LOCAL
After this just restart sql server service.
Thanks
Hari
SQL Server MVP
"Will Kubly" <wkubly@.wi.rr.com> wrote in message
news:uf%23cyMnjFHA.3704@.TK2MSFTNGP10.phx.gbl...
> Hi
> We are getting ready to replace an old NT old SQL server with a New
> Server, New Windows and SQL.
> I would like to setup the new server with a new name for testing and once
> we have it working rename it to the old server name. There are some ODBC
> connections that use the name and I suspect a few other things setup that
> way as well.
> Does that cause an issue with SQL to rename a server?
> Thanks
> Will

New SQL server to replace old SQL server

Hi
We are getting ready to replace an old NT old SQL server with a New
Server, New Windows and SQL.
I would like to setup the new server with a new name for testing and
once we have it working rename it to the old server name. There are some
ODBC connections that use the name and I suspect a few other things
setup that way as well.
Does that cause an issue with SQL to rename a server?
Thanks
WillHi,
After testing you can rename the sql server with out any issues.
Use:-
SP_DROPserver <servernaem>
Go
SP_ADDSERVER <name>,LOCAL
After this just restart sql server service.
Thanks
Hari
SQL Server MVP
"Will Kubly" <wkubly@.wi.rr.com> wrote in message
news:uf%23cyMnjFHA.3704@.TK2MSFTNGP10.phx.gbl...
> Hi
> We are getting ready to replace an old NT old SQL server with a New
> Server, New Windows and SQL.
> I would like to setup the new server with a new name for testing and once
> we have it working rename it to the old server name. There are some ODBC
> connections that use the name and I suspect a few other things setup that
> way as well.
> Does that cause an issue with SQL to rename a server?
> Thanks
> Willsql

New SQL server to replace old SQL server

Hi
We are getting ready to replace an old NT old SQL server with a New
Server, New Windows and SQL.
I would like to setup the new server with a new name for testing and
once we have it working rename it to the old server name. There are some
ODBC connections that use the name and I suspect a few other things
setup that way as well.
Does that cause an issue with SQL to rename a server?
Thanks
WillHi,
After testing you can rename the sql server with out any issues.
Use:-
SP_DROPserver <servernaem>
Go
SP_ADDSERVER <name>,LOCAL
After this just restart sql server service.
Thanks
Hari
SQL Server MVP
"Will Kubly" <wkubly@.wi.rr.com> wrote in message
news:uf%23cyMnjFHA.3704@.TK2MSFTNGP10.phx.gbl...
> Hi
> We are getting ready to replace an old NT old SQL server with a New
> Server, New Windows and SQL.
> I would like to setup the new server with a new name for testing and once
> we have it working rename it to the old server name. There are some ODBC
> connections that use the name and I suspect a few other things setup that
> way as well.
> Does that cause an issue with SQL to rename a server?
> Thanks
> Will

New SQL Server Setup - 32 or 64bit windows 2003?

Hi folks,
Just wondering if anyone can offer me any advice on a new SQL server
setup I am putting together. We are trying to squeeze as much
performance out of a new server as possible.
We are looking at getting a DL380 with a quad core xeon, 4gb ram and
looking to run windows 2003 server standard r2 edition. The question
is whether to go with the 32 bit
version of windows or the 64bit version. We will be running SQL 2000
in 32 bit mode anyway so is there really any benfit in running the 64
bit version of windows? One supplier has mentioned
that it isn't really worth it unless we are running with at least 8gb
of RAM in the machine. Anyone any ideas?
On the disk arrangements I am looking at the following setup. 2 x
72gb SAS drives RAID 1 running the system, 2 x 72gb SAS drives RAID 1
running the log files and then 3 x 146gb SAS drives
running the datafiles running RAID 5. What do you think? Is this
suitable?
Any tips or ideas greatfully received!
Thanks in advance
Hi
If you have 64bit processors that are are supported SQL Server, then using
64bit all the way through is going to give you better performance. I am not
sure why you rule out 64bit SQL Server?
John
"Fox1977" wrote:

> Hi folks,
> Just wondering if anyone can offer me any advice on a new SQL server
> setup I am putting together. We are trying to squeeze as much
> performance out of a new server as possible.
> We are looking at getting a DL380 with a quad core xeon, 4gb ram and
> looking to run windows 2003 server standard r2 edition. The question
> is whether to go with the 32 bit
> version of windows or the 64bit version. We will be running SQL 2000
> in 32 bit mode anyway so is there really any benfit in running the 64
> bit version of windows? One supplier has mentioned
> that it isn't really worth it unless we are running with at least 8gb
> of RAM in the machine. Anyone any ideas?
> On the disk arrangements I am looking at the following setup. 2 x
> 72gb SAS drives RAID 1 running the system, 2 x 72gb SAS drives RAID 1
> running the log files and then 3 x 146gb SAS drives
> running the datafiles running RAID 5. What do you think? Is this
> suitable?
> Any tips or ideas greatfully received!
> Thanks in advance
>
|||On 12 Mar, 08:48, John Bell <jbellnewspo...@.hotmail.com> wrote:[vbcol=seagreen]
> Hi
> If you have 64bit processors that are are supported SQL Server, then using
> 64bit all the way through is going to give you better performance. I am not
> sure why you rule out 64bit SQL Server?
> John
> "Fox1977" wrote:
>
>
Thanks John,
We have decided to take the plunge and go with x64 for server and SQL

New SQL Server Setup - 32 or 64bit windows 2003?

Hi folks,
Just wondering if anyone can offer me any advice on a new SQL server
setup I am putting together. We are trying to squeeze as much
performance out of a new server as possible.
We are looking at getting a DL380 with a quad core xeon, 4gb ram and
looking to run windows 2003 server standard r2 edition. The question
is whether to go with the 32 bit
version of windows or the 64bit version. We will be running SQL 2000
in 32 bit mode anyway so is there really any benfit in running the 64
bit version of windows? One supplier has mentioned
that it isn't really worth it unless we are running with at least 8gb
of RAM in the machine. Anyone any ideas?
On the disk arrangements I am looking at the following setup. 2 x
72gb SAS drives RAID 1 running the system, 2 x 72gb SAS drives RAID 1
running the log files and then 3 x 146gb SAS drives
running the datafiles running RAID 5. What do you think? Is this
suitable?
Any tips or ideas greatfully received!
Thanks in advanceHi
If you have 64bit processors that are are supported SQL Server, then using
64bit all the way through is going to give you better performance. I am not
sure why you rule out 64bit SQL Server?
John
"Fox1977" wrote:
> Hi folks,
> Just wondering if anyone can offer me any advice on a new SQL server
> setup I am putting together. We are trying to squeeze as much
> performance out of a new server as possible.
> We are looking at getting a DL380 with a quad core xeon, 4gb ram and
> looking to run windows 2003 server standard r2 edition. The question
> is whether to go with the 32 bit
> version of windows or the 64bit version. We will be running SQL 2000
> in 32 bit mode anyway so is there really any benfit in running the 64
> bit version of windows? One supplier has mentioned
> that it isn't really worth it unless we are running with at least 8gb
> of RAM in the machine. Anyone any ideas?
> On the disk arrangements I am looking at the following setup. 2 x
> 72gb SAS drives RAID 1 running the system, 2 x 72gb SAS drives RAID 1
> running the log files and then 3 x 146gb SAS drives
> running the datafiles running RAID 5. What do you think? Is this
> suitable?
> Any tips or ideas greatfully received!
> Thanks in advance
>|||On 12 Mar, 08:48, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> If you have 64bit processors that are are supported SQL Server, then using
> 64bit all the way through is going to give you better performance. I am not
> sure why you rule out 64bit SQL Server?
> John
> "Fox1977" wrote:
> > Hi folks,
> > Just wondering if anyone can offer me any advice on a new SQL server
> > setup I am putting together. We are trying to squeeze as much
> > performance out of a new server as possible.
> > We are looking at getting a DL380 with a quad core xeon, 4gb ram and
> > looking to run windows 2003 server standard r2 edition. The question
> > is whether to go with the 32 bit
> > version of windows or the 64bit version. We will be running SQL 2000
> > in 32 bit mode anyway so is there really any benfit in running the 64
> > bit version of windows? One supplier has mentioned
> > that it isn't really worth it unless we are running with at least 8gb
> > of RAM in the machine. Anyone any ideas?
> > On the disk arrangements I am looking at the following setup. 2 x
> > 72gb SAS drives RAID 1 running the system, 2 x 72gb SAS drives RAID 1
> > running the log files and then 3 x 146gb SAS drives
> > running the datafiles running RAID 5. What do you think? Is this
> > suitable?
> > Any tips or ideas greatfully received!
> > Thanks in advance
Thanks John,
We have decided to take the plunge and go with x64 for server and SQL

New SQL Server Registration failure

Hi,

I have 3 SQL Servers running here. Here are their configurations:

SERVER 1:
OS: Windows 2000 SP 4
SQL: SQL Server 2000 SP 4

SERVER 2:
OS: Windows 2000 SP 4
SQL: SQL Server 2000 SP 4

SERVER 3:
OS: Windows XP Professionnal
SQL: SQL Server 2000 SP 3

Now, as you can see, SERVER 1 and SERVER 2 have identical configurations. Plus, both will accept Windows Authentication and SQL Authentication.

If I try to add a new Registration from SERVER 3 to SERVER 1, it works fine but from SERVER 3 to SERVER 2 it doesn't. I always get an error (SQL Server does not exist or access denied). But, using the exact same user name and password, a connection can be established from SERVER 1 to SERVER 2 and vice-versa. Only when trying to connect froms SERVER 3 to SERVER 2 fails.

Any ideas?

Thanks,

Skip.I thought we only have sp3a in sql 2000. Where did you get the sp4?|||Originally posted by joejcheng
I thought we only have sp3a in sql 2000. Where did you get the sp4?

I don't know, I'm not the sysadmin responsible for updating software. It's just what is says in the about menu option.

Skip.

New SQL Server Install Advice

I have a new Dell PowerEdge 2800 running windows 2003. I have 2 RAID
containers as the machine has a PERC 4 controller. The machine has x2 73GB
SCSI and x4 146GB SCSI HDD.
Container 1
--
The OS C drive (partition of 12GB) is in RAID 1 and so is E drive which has
56GB free.
Container 2
--
A D drive for Data I created and also L for Log which I assigned as dynamic
drives.
Is this setup Ok for running SQL2000. The Data files will reside in D and
the Log files will reside in L. Is this Ok for the read/write access that
occurs when SQL is accessed?
Please help.
skcI assume there is at least one processor and some memory on the server as
well.
It will work. It depends on what performance, capacity, and availability
you are needing.
"Skc" <Skc@.discussions.microsoft.com> wrote in message
news:46CDFADB-7AC6-4719-B0A8-8154D6977397@.microsoft.com...
>I have a new Dell PowerEdge 2800 running windows 2003. I have 2 RAID
> containers as the machine has a PERC 4 controller. The machine has x2
> 73GB
> SCSI and x4 146GB SCSI HDD.
> Container 1
> --
> The OS C drive (partition of 12GB) is in RAID 1 and so is E drive which
> has
> 56GB free.
> Container 2
> --
> A D drive for Data I created and also L for Log which I assigned as
> dynamic
> drives.
> Is this setup Ok for running SQL2000. The Data files will reside in D and
> the Log files will reside in L. Is this Ok for the read/write access that
> occurs when SQL is accessed?
> Please help.
> skc|||Xeon 2.8 x2 and 2GB RAM.
We want max. performance. Is this OK?
Furthermore, I installed SQL2000 and it came with 4 CDs:
1> SQL 2000 Standard (Personal)
2> SQL 2000 Standard
3> SP4
4> Reporting Tools
I installed Disk #1, asked me no product key, I selected 5 CALS from the
dropdown (which was how many I bought) and that was it. I have the SQL
Service running and the SQL Tools (enterprise manager). What is the
difference between the 2 Cds mentioned above?
In Enterprise Manager, when I right-click the (local) Server, it says I have
Microsoft SQL Server Std Edition installed. This is very odd, I hope I have
done this right as it did not ask for a serial product key or anything.
Please verify the above it OK.
"Danny" wrote:

> I assume there is at least one processor and some memory on the server as
> well.
> It will work. It depends on what performance, capacity, and availability
> you are needing.
> "Skc" <Skc@.discussions.microsoft.com> wrote in message
> news:46CDFADB-7AC6-4719-B0A8-8154D6977397@.microsoft.com...
>
>

New SQL Server Install Advice

I have a new Dell PowerEdge 2800 running windows 2003. I have 2 RAID
containers as the machine has a PERC 4 controller. The machine has x2 73GB
SCSI and x4 146GB SCSI HDD.
Container 1
The OS C drive (partition of 12GB) is in RAID 1 and so is E drive which has
56GB free.
Container 2
A D drive for Data I created and also L for Log which I assigned as dynamic
drives.
Is this setup Ok for running SQL2000. The Data files will reside in D and
the Log files will reside in L. Is this Ok for the read/write access that
occurs when SQL is accessed?
Please help.
skc
I assume there is at least one processor and some memory on the server as
well.
It will work. It depends on what performance, capacity, and availability
you are needing.
"Skc" <Skc@.discussions.microsoft.com> wrote in message
news:46CDFADB-7AC6-4719-B0A8-8154D6977397@.microsoft.com...
>I have a new Dell PowerEdge 2800 running windows 2003. I have 2 RAID
> containers as the machine has a PERC 4 controller. The machine has x2
> 73GB
> SCSI and x4 146GB SCSI HDD.
> Container 1
> --
> The OS C drive (partition of 12GB) is in RAID 1 and so is E drive which
> has
> 56GB free.
> Container 2
> --
> A D drive for Data I created and also L for Log which I assigned as
> dynamic
> drives.
> Is this setup Ok for running SQL2000. The Data files will reside in D and
> the Log files will reside in L. Is this Ok for the read/write access that
> occurs when SQL is accessed?
> Please help.
> skc
|||Xeon 2.8 x2 and 2GB RAM.
We want max. performance. Is this OK?
Furthermore, I installed SQL2000 and it came with 4 CDs:
1> SQL 2000 Standard (Personal)
2> SQL 2000 Standard
3> SP4
4> Reporting Tools
I installed Disk #1, asked me no product key, I selected 5 CALS from the
dropdown (which was how many I bought) and that was it. I have the SQL
Service running and the SQL Tools (enterprise manager). What is the
difference between the 2 Cds mentioned above?
In Enterprise Manager, when I right-click the (local) Server, it says I have
Microsoft SQL Server Std Edition installed. This is very odd, I hope I have
done this right as it did not ask for a serial product key or anything.
Please verify the above it OK.
"Danny" wrote:

> I assume there is at least one processor and some memory on the server as
> well.
> It will work. It depends on what performance, capacity, and availability
> you are needing.
> "Skc" <Skc@.discussions.microsoft.com> wrote in message
> news:46CDFADB-7AC6-4719-B0A8-8154D6977397@.microsoft.com...
>
>

New SQL Server Install Advice

I have a new Dell PowerEdge 2800 running windows 2003. I have 2 RAID
containers as the machine has a PERC 4 controller. The machine has x2 73GB
SCSI and x4 146GB SCSI HDD.
Container 1
--
The OS C drive (partition of 12GB) is in RAID 1 and so is E drive which has
56GB free.
Container 2
--
A D drive for Data I created and also L for Log which I assigned as dynamic
drives.
Is this setup Ok for running SQL2000. The Data files will reside in D and
the Log files will reside in L. Is this Ok for the read/write access that
occurs when SQL is accessed?
Please help.
skcI assume there is at least one processor and some memory on the server as
well.
It will work. It depends on what performance, capacity, and availability
you are needing.
"Skc" <Skc@.discussions.microsoft.com> wrote in message
news:46CDFADB-7AC6-4719-B0A8-8154D6977397@.microsoft.com...
>I have a new Dell PowerEdge 2800 running windows 2003. I have 2 RAID
> containers as the machine has a PERC 4 controller. The machine has x2
> 73GB
> SCSI and x4 146GB SCSI HDD.
> Container 1
> --
> The OS C drive (partition of 12GB) is in RAID 1 and so is E drive which
> has
> 56GB free.
> Container 2
> --
> A D drive for Data I created and also L for Log which I assigned as
> dynamic
> drives.
> Is this setup Ok for running SQL2000. The Data files will reside in D and
> the Log files will reside in L. Is this Ok for the read/write access that
> occurs when SQL is accessed?
> Please help.
> skc|||Xeon 2.8 x2 and 2GB RAM.
We want max. performance. Is this OK?
Furthermore, I installed SQL2000 and it came with 4 CDs:
1> SQL 2000 Standard (Personal)
2> SQL 2000 Standard
3> SP4
4> Reporting Tools
I installed Disk #1, asked me no product key, I selected 5 CALS from the
dropdown (which was how many I bought) and that was it. I have the SQL
Service running and the SQL Tools (enterprise manager). What is the
difference between the 2 Cds mentioned above?
In Enterprise Manager, when I right-click the (local) Server, it says I have
Microsoft SQL Server Std Edition installed. This is very odd, I hope I have
done this right as it did not ask for a serial product key or anything.
Please verify the above it OK.
"Danny" wrote:
> I assume there is at least one processor and some memory on the server as
> well.
> It will work. It depends on what performance, capacity, and availability
> you are needing.
> "Skc" <Skc@.discussions.microsoft.com> wrote in message
> news:46CDFADB-7AC6-4719-B0A8-8154D6977397@.microsoft.com...
> >I have a new Dell PowerEdge 2800 running windows 2003. I have 2 RAID
> > containers as the machine has a PERC 4 controller. The machine has x2
> > 73GB
> > SCSI and x4 146GB SCSI HDD.
> >
> > Container 1
> > --
> > The OS C drive (partition of 12GB) is in RAID 1 and so is E drive which
> > has
> > 56GB free.
> >
> > Container 2
> > --
> > A D drive for Data I created and also L for Log which I assigned as
> > dynamic
> > drives.
> >
> > Is this setup Ok for running SQL2000. The Data files will reside in D and
> > the Log files will reside in L. Is this Ok for the read/write access that
> > occurs when SQL is accessed?
> >
> > Please help.
> >
> > skc
>
>

New Sql Server Cluster Install

Everyone,
I'm installing SQL Server 2000 SP2 virtual server onto a Windows 2003
Cluster. The install process seems to install sql server fine on both
machines, however when the installer gets to creating the virtual resources
the install fails after about 5 to 10 minutes. I've looked at the sql logs
that are generated by the install and the only error code I see that is not 0
is an error trying to load a dll. After the install fails the installer
proceeds to uninstall all files and shortcuts from both nodes. I'm thinking
this has something to do with Windows 2003 not allowing anything less than
sp3 to start. Can anyone help clarify this for me. I've searched google and
have found many articles and kb about other issues but none so far that look
like this one. If this is caused by the sp3 issues is there a workaround or
is there a way to get an install CD of SQL Server 2000 with SP3.
Thanks!
ST
Hi
Installing sp2 is no problem unless you don't patch it to sp3a after the
install completes.
Make sure you have gone through the check lists on
http://www.microsoft.com/technet/pro.../failclus.mspx
Regards
Mike
"Shannon T." wrote:

> Everyone,
> I'm installing SQL Server 2000 SP2 virtual server onto a Windows 2003
> Cluster. The install process seems to install sql server fine on both
> machines, however when the installer gets to creating the virtual resources
> the install fails after about 5 to 10 minutes. I've looked at the sql logs
> that are generated by the install and the only error code I see that is not 0
> is an error trying to load a dll. After the install fails the installer
> proceeds to uninstall all files and shortcuts from both nodes. I'm thinking
> this has something to do with Windows 2003 not allowing anything less than
> sp3 to start. Can anyone help clarify this for me. I've searched google and
> have found many articles and kb about other issues but none so far that look
> like this one. If this is caused by the sp3 issues is there a workaround or
> is there a way to get an install CD of SQL Server 2000 with SP3.
> --
> Thanks!
> ST
|||The error I'm receiving I looks like it is during the self registration phase.
The error is as follows:
09:13:43 C:\PROGRA~1\MICROS~1\80\Tools\Binn\dcomscm.exe /RegServer
09:13:43 Process Exit Code: (0)
09:13:43 C:\PROGRA~1\COMMON~1\MICROS~1\SQLDEB~1\sqldbreg.ex e -RegServer
09:13:43 Process Exit Code: (-2147312566) Error loading type library/DLL.
|||this seems to be the tsql debugger. Please refer to
http://support.microsoft.com/default...b;en-us;280101 for some
information on this.
Unless you are running tsql debugger in your clustered (production?)
environment, I doubt you would need this.
What components are you selecting in your install? Are you installing the
developers resources and code samples? It seems to me that this component is
probably installed with them as opposed to the default installation set.
"Shannon T." <ShannonT@.discussions.microsoft.com> wrote in message
news:E753DEF8-46B7-408E-BBCB-E6FE3A6A14D1@.microsoft.com...
> The error I'm receiving I looks like it is during the self registration
> phase.
> The error is as follows:
> 09:13:43 C:\PROGRA~1\MICROS~1\80\Tools\Binn\dcomscm.exe /RegServer
> 09:13:43 Process Exit Code: (0)
> 09:13:43 C:\PROGRA~1\COMMON~1\MICROS~1\SQLDEB~1\sqldbreg.ex e -RegServer
> 09:13:43 Process Exit Code: (-2147312566) Error loading type library/DLL.
>
>
|||I choose the default installation radio button on the Select Type window
during the setup. Should I use the custom install type for a virtual server?
"Hilary Cotter" wrote:

> this seems to be the tsql debugger. Please refer to
> http://support.microsoft.com/default...b;en-us;280101 for some
> information on this.
> Unless you are running tsql debugger in your clustered (production?)
> environment, I doubt you would need this.
> What components are you selecting in your install? Are you installing the
> developers resources and code samples? It seems to me that this component is
> probably installed with them as opposed to the default installation set.
> "Shannon T." <ShannonT@.discussions.microsoft.com> wrote in message
> news:E753DEF8-46B7-408E-BBCB-E6FE3A6A14D1@.microsoft.com...
>
>
|||I have removed the sql debug tools from the install. The error that was
showing up is no longer occuring. However, I still receive a message that the
installation has failed and the install rolls back.
I'm totally confused. Here is the log if anyone sees anything wrong please
let me know.
14:40:20 Begin Setup
14:40:20 8.00.194
14:40:20 Mode = Silent
14:40:20 ModeType = CLUSTER
14:40:20 Cluster node.
14:40:20 g_szIssPath=C:\WINDOWS\setup~0.iss
14:40:20 GetDefinitionEx returned: 0, Extended: 0x0
14:40:20 ValueFTS returned: 1
14:40:20 ValuePID returned: 1
14:40:20 ValueLic returned: 1
14:40:20 System: Windows NT Enterprise Server
14:40:20 SQL Server ProductType: Enterprise Edition [0x3]
14:40:20 IsNTCluster returned: 1
14:40:20 Begin Action: SetupInitialize
14:40:20 End Action SetupInitialize
14:40:20 Begin Action: SetupInstall
14:40:20 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir ...
14:40:20 CommonFilesDir=C:\Program Files\Common Files
14:40:20 Windows Directory=C:\WINDOWS\
14:40:20 Program Files=C:\Program Files\
14:40:20 TEMPDIR=C:\DOCUME~1\username\LOCALS~1\Temp\
14:40:20 Begin Action: SetupInstall
14:40:20 digpid size : 256
14:40:20 digpid size : 164
14:40:20 Begin Action: CheckFixedRequirements
14:40:20 Platform ID: 0xf00000
14:40:20 Version: 5.2.3790
14:40:20 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.186
14:40:20 End Action: CheckFixedRequirements
14:40:20 Begin Action: ShowDialogs
14:40:20 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
14:40:20 Begin Action ShowDialogsHlpr: 0x1
14:40:20 Begin Action: DialogShowSdWelcome
14:40:20 End Action DialogShowSdWelcome
14:40:20 Dialog 0x1 returned: 1
14:40:20 End Action ShowDialogsHlpr
14:40:20 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
14:40:20 Begin Action ShowDialogsHlpr: 0x2
14:40:20 Begin Action: DialogShowSdMachineName
14:40:20 [DlgMachine]
14:40:20 Result = 1
14:40:20 Type = 268435466
14:40:20 Name = virtualserver1
14:40:20 ShowDlgMachine returned: 1
14:40:20 Name = virtualserver1, Type = 0x1000000a
14:40:20 Begin Action: CheckRequirements
14:40:20 Processor Architecture: x86 (Pentium)
14:40:20 ComputerName: virtualserver1
14:40:20 User Name: username
14:40:20 IsAllAccessAllowed returned: 1
14:40:20 OS Language: 0x409
14:40:20 End Action CheckRequirements
14:40:20 This combination of Package and Operating System allows a full
product install.
14:40:20 End Action DialogShowSdMachineName
14:40:20 begin ShowDialogsUpdateMask
14:40:20 nFullMask = 0x183000f7, nCurrent = 0x2, nDirection = 0
14:40:20 Updated Dialog Mask: 0xbf3c037, Disable Back = 0x1
14:40:20 Dialog 0x2 returned: 0
14:40:20 End Action ShowDialogsHlpr
14:40:20 ShowDialogsGetDialog returned: nCurrent=0x4,index=2
14:40:20 Begin Action ShowDialogsHlpr: 0x4
14:40:20 Begin Action: DialogShowSdInstallMode
14:40:20 [DlgInstallMode]
14:40:20 Result = 1
14:40:20 Type = 1
14:40:20 InstallMode : 0x1
14:40:20 End Action DialogShowSdInstallMode
14:40:20 begin ShowDialogsUpdateMask
14:40:20 nFullMask = 0xbf3c037, nCurrent = 0x4, nDirection = 1
14:40:20 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
14:40:20 Dialog 0x4 returned: 1
14:40:20 End Action ShowDialogsHlpr
14:40:20 ShowDialogsGetDialog returned: nCurrent=0x10,index=4
14:40:20 Begin Action ShowDialogsHlpr: 0x10
14:40:20 Begin Action: DialogShowSdRegisterUserEx
14:40:20 End Action DialogShowSdRegisterUserEx
14:40:20 begin ShowDialogsUpdateMask
14:40:20 nFullMask = 0x1bf7c037, nCurrent = 0x10, nDirection = 1
14:40:20 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
14:40:20 Dialog 0x10 returned: 1
14:40:20 End Action ShowDialogsHlpr
14:40:20 ShowDialogsGetDialog returned: nCurrent=0x20,index=5
14:40:20 Begin Action ShowDialogsHlpr: 0x20
14:40:20 Begin Action: DialogShowSdLicense
14:40:20 End Action DialogShowSdLicense
14:40:20 Dialog 0x20 returned: 1
14:40:20 End Action ShowDialogsHlpr
14:40:20 ShowDialogsGetDialog returned: nCurrent=0x4000,index=14
14:40:20 Begin Action ShowDialogsHlpr: 0x4000
14:40:20 Begin Action: DialogShowSdVirtualServer
14:40:20 [DlgVirtServer]
14:40:20 Result = 1
14:40:20 VirtServerName = virtualserver
14:40:20 IpAddresses = 10.130.19.135,255.255.252.0,Public
14:40:24 ShowDlgVirtualServer returned: 0
14:40:24 Ipaddress = 10.130.19.135,255.255.252.0,Public
14:40:24 szNewList = 10.130.19.135,255.255.252.0,Public
14:40:24 szModifiedList =
14:40:24 szRemovedList =
14:40:24 End Action DialogShowSdVirtualServer
14:40:24 begin ShowDialogsUpdateMask
14:40:24 nFullMask = 0x1bf7c037, nCurrent = 0x4000, nDirection = 1
14:40:24 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
14:40:24 Dialog 0x4000 returned: 1
14:40:24 End Action ShowDialogsHlpr
14:40:24 ShowDialogsGetDialog returned: nCurrent=0x8000,index=15
14:40:24 Begin Action ShowDialogsHlpr: 0x8000
14:40:24 Begin Action : DialogShowSdDiskGroups
14:40:24 [DlgDiskGroups]
14:40:24 Result = 1
14:40:24 DiskGroupsName = SQLGroup
14:40:24 ShowDlgDiskGroups returned: 1
14:40:24 Disk Group = SQLGroup
14:40:24 End Action : DialogShowSdDiskGroups
14:40:24 begin ShowDialogsUpdateMask
14:40:24 nFullMask = 0x1bf7c037, nCurrent = 0x8000, nDirection = 1
14:40:24 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
14:40:24 Dialog 0x8000 returned: 1
14:40:24 End Action ShowDialogsHlpr
14:40:24 ShowDialogsGetDialog returned: nCurrent=0x10000,index=16
14:40:24 Begin Action ShowDialogsHlpr: 0x10000
14:40:24 Begin Action: DialogShowSdClusterDef
14:40:24 [DlgClusterDef]
14:40:24 Result = 1
14:40:24 nNumNodes = 2
14:40:24 VirtServerName = virtualserver
14:40:24 szPrefowners = virtualserver1,virtualserver2
14:40:24 ShowDlgClusterDef returned: 1
14:40:24 PrefOwners = virtualserver1,virtualserver2, NumIp = 0
14:40:24 End Action DialogShowSdClusterDef
14:40:24 begin ShowDialogsUpdateMask
14:40:24 nFullMask = 0x1bf7c037, nCurrent = 0x10000, nDirection = 1
14:40:24 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
14:40:24 Dialog 0x10000 returned: 1
14:40:24 End Action ShowDialogsHlpr
14:40:24 ShowDialogsGetDialog returned: nCurrent=0x20000,index=17
14:40:24 Begin Action ShowDialogsHlpr: 0x20000
14:40:24 Begin Action : Cluster Security - DlgAcct
14:40:24 [DlgAccount]
14:40:24 Result = 1
14:40:24 Domain = TMC
14:40:24 DomainAcct = username
14:40:24 DomainPwd
14:40:24 ValidateUser returned: 1, 0, 0x17c
14:40:24 IsAcctValidForCluster returned: 1, 0
14:40:24 End Action : Cluster Security - DlgAcct
14:40:24 begin ShowDialogsUpdateMask
14:40:24 nFullMask = 0x1bf7c037, nCurrent = 0x20000, nDirection = 1
14:40:24 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
14:40:24 Dialog 0x20000 returned: 1
14:40:24 End Action ShowDialogsHlpr
14:40:24 ShowDialogsGetDialog returned: nCurrent=0x40000,index=18
14:40:24 Begin Action ShowDialogsHlpr: 0x40000
14:40:24 Begin Action: DialogShowSdCliSvr
14:40:24 DisplaySystemPreReq
14:40:24 [DlgClientServer]
14:40:24 Result = 1
14:40:24 Type = 2
14:40:24 ShowDlgClientServerSelect returned: 1
14:40:24 Type : 0x2
14:40:24 End Action DialogShowSdCliSvr
14:40:24 begin ShowDialogsUpdateMask
14:40:24 nFullMask = 0x1bf7c037, nCurrent = 0x40000, nDirection = 1
14:40:24 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:24 Dialog 0x40000 returned: 1
14:40:24 End Action ShowDialogsHlpr
14:40:24 ShowDialogsGetDialog returned: nCurrent=0x80000,index=19
14:40:24 Begin Action ShowDialogsHlpr: 0x80000
14:40:24 Begin Action: DialogShowSdInstanceName
14:40:24 [DlgInstanceName]
14:40:24 Result = 1
14:40:24 InstanceName = MSSQLSERVER
14:40:24 Begin Action: ShowDlgInstanceName
14:40:24 End Action: ShowDlgInstanceName
14:40:24 ShowDlgInstanceName returned : 1
14:40:24 InstanceName : MSSQLSERVER
14:40:24 CreateSetupTopology(virtualserver1), Handle : 0x1453f00, returned : 0
14:40:24 CreateSetupTopology returned : 0, Handle : 0x1453f00
14:40:24 Topology Type : 1, Return Value : 0
14:40:24 ST_GetPhysicalNode returned : 0, PNHandle : 0x1453f50
14:40:24 PN_EnumerateEx returned : 0
14:40:24 PN_GetSQLStates returned : 0, SqlStates : 0x0
14:40:24 PN_StartScan [0x1453f50] returned : 0
14:40:24 PN_GetNext [0x1453f50] returned : 18, Handle: [0x0]
14:40:24 No more items in enumeration.
14:40:24 ReleaseSetupTopology
14:40:24 End Action DialogShowSdInstanceName
14:40:24 begin ShowDialogsUpdateMask
14:40:24 nFullMask = 0x1bffc037, nCurrent = 0x80000, nDirection = 1
14:40:24 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:24 Dialog 0x80000 returned: 1
14:40:24 End Action ShowDialogsHlpr
14:40:24 ShowDialogsGetDialog returned: nCurrent=0x100000,index=20
14:40:24 Begin Action ShowDialogsHlpr: 0x100000
14:40:24 Begin Action: DialogShowSdSetupType
14:40:24 Begin Action: Setup Type
14:40:24 [SetupTypeSQL]
14:40:24 Result = 303
14:40:24 szDir = C:\Program Files\Microsoft SQL Server
14:40:24 final szDir = C:\Program Files\Microsoft SQL Server
14:40:24 szDataDir = g:\dbfiles
14:40:25 final szDataDir = g:\dbfiles
14:40:25 End Action: Setup Type
14:40:25 Setup Type: Custom (303)
14:40:25 End Action DialogShowSdSetupType
14:40:25 begin ShowDialogsUpdateMask
14:40:25 nFullMask = 0x1bffc037, nCurrent = 0x100000, nDirection = 303
14:40:25 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:25 Dialog 0x100000 returned: 303
14:40:25 End Action ShowDialogsHlpr
14:40:25 ShowDialogsGetDialog returned: nCurrent=0x200000,index=21
14:40:25 Begin Action ShowDialogsHlpr: 0x200000
14:40:25 Begin Action: DialogShowSdComponentMult
14:40:25 basesys = 0, baseinst = 0, basedata = 0
14:40:25 Begin Action: Component Handler
14:40:25 ***** Silent Mode in Multi comps
14:40:25 [SQLComponentMult]
14:40:25 Result = 1
14:40:25 ComponentSelectItem(MgtTool\Wzcnflct): -103
14:40:25 End Action: Component Handler
14:40:25 End Action DialogShowSdComponentMult
14:40:25 begin ShowDialogsUpdateMask
14:40:25 nFullMask = 0x1bffc037, nCurrent = 0x200000, nDirection = 1
14:40:25 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:25 Dialog 0x200000 returned: 1
14:40:25 End Action ShowDialogsHlpr
14:40:25 ShowDialogsGetDialog returned: nCurrent=0x400000,index=22
14:40:25 Begin Action ShowDialogsHlpr: 0x400000
14:40:25 Begin Action: DlgServices
14:40:25 [DlgServices]
14:40:25 Result = 1
14:40:25 Local-Domain = 61680
14:40:25 AutoStart = 0
14:40:25 SQLDomain= TMC
14:40:25 SQLDomainAcct = bob
14:40:25 SQLDomainPwd
14:40:25 ValidateUser returned: 1, 0, 0x17c
14:40:25 GrantRightAsService returned : 1, 0
14:40:25 AgtDomain= TMC
14:40:25 AgtDomainAcct= bob
14:40:25 AgtDomainPwd
14:40:25 ValidateUser returned: 1, 0, 0x180
14:40:25 GrantRightAsService returned : 1, 0
14:40:25 End Action DlgServices
14:40:25 begin ShowDialogsUpdateMask
14:40:25 nFullMask = 0x1bffc037, nCurrent = 0x400000, nDirection = 1
14:40:25 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:25 Dialog 0x400000 returned: 1
14:40:25 End Action ShowDialogsHlpr
14:40:25 ShowDialogsGetDialog returned: nCurrent=0x800000,index=23
14:40:25 Begin Action ShowDialogsHlpr: 0x800000
14:40:25 Begin Action: DlgSQLSecurity
14:40:25 [DlgSQLSecurity]
14:40:25 Result = 1
14:40:25 szPwd
14:40:25 ShowDlgSQLSecurity returned: 1
14:40:25 LoginMode = 2,szPwd
14:40:25 End Action DlgSQLSecurity
14:40:25 begin ShowDialogsUpdateMask
14:40:25 nFullMask = 0x1bffc037, nCurrent = 0x800000, nDirection = 1
14:40:25 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:25 Dialog 0x800000 returned: 1
14:40:25 End Action ShowDialogsHlpr
14:40:25 ShowDialogsGetDialog returned: nCurrent=0x1000000,index=24
14:40:25 Begin Action ShowDialogsHlpr: 0x1000000
14:40:25 Begin Action: DlgCollation
14:40:25 [DlgCollation]
14:40:25 Result = 1
14:40:25 collation_name = SQL_Latin1_General_CP1_CI_AS
14:40:25 ShowDlgCollation returned: 1
14:40:25 collation_name = SQL_Latin1_General_CP1_CI_AS,locale_name = ,lcid =
0x0,SortId = 0,dwCompFlags = 0x0
14:40:25 End Action DlgCollation
14:40:25 begin ShowDialogsUpdateMask
14:40:25 nFullMask = 0x1bffc037, nCurrent = 0x1000000, nDirection = 1
14:40:25 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:25 Dialog 0x1000000 returned: 1
14:40:25 End Action ShowDialogsHlpr
14:40:25 ShowDialogsGetDialog returned: nCurrent=0x2000000,index=25
14:40:25 Begin Action ShowDialogsHlpr: 0x2000000
14:40:25 Begin Action: DlgNetwork
14:40:25 Result = 1
14:40:25 [DlgServerNetwork]
14:40:25 NetworkLibs = 255
14:40:25 TCPPort =1433
14:40:25 TCPPrxy =
14:40:25 NMPPipeName =\\.\pipe\sql\query
14:40:25 ShowDlgNetwork returned: 1
14:40:25 [DlgServerNetwork]
14:40:25 NetworkLibs = 255
14:40:25 TCPPort = 1433
14:40:25 TCPPrxy = Default
14:40:25 NMPPipeName = \\.\pipe\sql\query
14:40:25 Result = 1
14:40:25 End Action DlgNetwork
14:40:25 begin ShowDialogsUpdateMask
14:40:25 nFullMask = 0x1bffc037, nCurrent = 0x2000000, nDirection = 1
14:40:25 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:25 Dialog 0x2000000 returned: 1
14:40:25 End Action ShowDialogsHlpr
14:40:25 ShowDialogsGetDialog returned: nCurrent=0x8000000,index=27
14:40:25 Begin Action ShowDialogsHlpr: 0x8000000
14:40:25 Begin Action: DialogShowSdStartCopy
14:40:25 End Action DialogShowSdStartCopy
14:40:25 begin ShowDialogsUpdateMask
14:40:25 nFullMask = 0x1bffc037, nCurrent = 0x8000000, nDirection = 1
14:40:25 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:25 Dialog 0x8000000 returned: 1
14:40:25 End Action ShowDialogsHlpr
14:40:25 ShowDialogsGetDialog returned: nCurrent=0x10000000,index=28
14:40:25 Begin Action ShowDialogsHlpr: 0x10000000
14:40:25 Begin Action: DialogShowSdLicenseMode
14:40:25 LicenseMode as read from ISS file : PERDEVICE
14:40:25 LicenseLimit as read from ISS file : 2
14:40:25 ShowDlgLicense returned: 1
14:40:25 ShowDlgLicense returned: LicenseMode = 0, LicenseLimit = 2
14:40:25 End Action DialogShowSdLicenseMode
14:40:25 Dialog 0x10000000 returned: 1
14:40:25 End Action ShowDialogsHlpr
14:40:25 ShowDialogsGetDialog returned: nCurrent=0x0,index=0
14:40:25 End Action ShowDialogs
14:40:25 Begin Action ProcessBeforeDataMove:
14:40:25 DeinstallStart returned (C:\Program Files\Microsoft SQL
Server\MSSQL): 0
14:40:25 End Action ProcessBeforeDataMove:
14:40:25 Begin Action SetToolsComponentSelection:
14:40:25 CreateSetupTopology(virtualserver1), Handle : 0x1453f00, returned : 0
14:40:25 CreateSetupTopology returned : 0, Handle : 0x1453f00
14:40:25 Topology Type : 1, Return Value : 0
14:40:25 ST_GetPhysicalNode returned : 0, PNHandle : 0x1453f50
14:40:25 PN_EnumerateEx returned : 0
14:40:25 PN_GetSQLStates returned : 0, SqlStates : 0x0
14:40:25 PN_StartScan [0x1453f50] returned : 0
14:40:25 PN_GetNext [0x1453f50] returned : 18, Handle: [0x0]
14:40:25 No more items in enumeration.
14:40:25 ReleaseSetupTopology
14:40:25 End Action SetToolsComponentSelection:
14:40:25 Begin Action ProcessComponentSelection:
14:40:25 End Action ProcessComponentSelection
14:40:25 Begin Action LogSelectedComponents:
...
14:40:25 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
14:40:25 End Action LogSelectedComponents
14:40:25 SQL program folder: C:\Program Files\Microsoft SQL Server\MSSQL
14:40:25 SQL data folder: g:\dbfiles\MSSQL
14:40:25 Windows system folder: C:\WINDOWS\system32\
14:40:25 Prog req: 21962, Data req: 31360, Sys req: 60946
14:40:25 Prog avail: 5778608, Data avail: 560472816, Sys avail: 5778608
14:40:25 Prog req vs. avail, 82908, 5778608
14:40:25 Data req vs. avail, 31360, 560472816
14:40:25 Sys req vs. avail, 60946, 5778608
14:40:25 DisplaySystemPreReq
14:40:25 Begin Action InstallPkgs:
14:40:25 Begin Action: Locked Connectivity Files Check
14:40:26 ConnectivityLocked returned: 0
14:40:26 The operation completed successfully.
14:40:26 End Action: Locked Connectivity Files Check
14:40:26 Setup is installing Microsoft Data Access Components (MDAC) ...
14:40:26 C:\SQL2000_Ent\x86\Other\sqlredis.exe /q:a
14:40:33 ExitCode: 0
14:40:33 InstallMSSearch instance: MSSQLSERVER
14:40:33 Software\Microsoft\Search\Install:Version not present
14:40:33 MSSearch 2.0 or greater version check returned -1
14:40:33 Setup is installing the Microsoft Full-Text Search Engine ...
14:40:33 "C:\SQL2000_Ent\x86\FullText\MSSearch\Search\Searc hStp.exe" /s
/a:SQLServer
14:40:42 Process Exit Code: (0)
14:41:03 End Action InstallPkgs
14:41:03 Begin Action MoveFileData:
14:41:03 Enabled SELFREGISTERBATCH
14:41:03 Enabled CORECOMPONENTHANDLING
14:41:25 Begin Action: MoveFileDataSpecial
14:41:25 End Action: MoveFileDataSpecial
14:41:25 End Action MoveFileData
14:41:25 Begin Action ProcessAfterDataMove:
14:41:25 End Action ProcessAfterDataMove
14:41:25 Begin Action BuildServer:
14:41:25 C:\DOCUME~1\Username\LOCALS~1\Temp\SqlSetup\Bin\sc m.exe -Silent 1
-Action 5 -ExePath "C:\Program Files\Microsoft SQL
Server\MSSQL\binn\sqlservr.exe" -Service "MSSQLSERVER"
14:41:25 Process Exit Code: (0)
14:41:25 Begin Action: CreateRegistrySetSQL
14:41:25 End Action: CreateRegistrySetSQL
14:41:25 Begin Action: RegWriteSetupEntry
14:41:25 End Action: RegWriteSetupEntry
14:41:25 Begin Action: CreateSer
14:41:25 End Action: CreateSer
14:41:25 Begin Action: SkuIt
14:41:25 End Action: SkuIt
14:41:25 SetFileSecuritySQLAndAdmin for g:\dbfiles\MSSQL returned: 0, 0
14:41:26 SetFileSecuritySQLAndAdmin for C:\Program Files\Microsoft SQL
Server\MSSQL returned: 0, 0
14:41:26 SetRegSecuritySQLAndAdmin for
Software\Microsoft\MSSQLServer\MSSQLServer returned: 0, 0
14:41:26 Begin Action: UpdateSystemPath
14:41:26 Path successfully updated.
14:41:26 C:\Program
Files\EMC\PowerPath\;%SystemRoot%\system32;%System Root%;%SystemRoot%\System32\Wbem;C:\Program
Files\Dell\OpenManage\Array Manager;C:\Program Files\Microsoft SQL
Server\80\Tools\BINN
14:41:26 End Action: UpdateSystemPath
14:41:26 Grant Right for TMC\bob returned : 1, 0
14:41:26 Grant Right for TMC\bob returned : 1, 0
14:41:26 Grant Right for TMC\bob returned : 1, 0
14:41:26 Grant Right for TMC\bob returned : 1, 0
14:41:26 Grant Right for TMC\bob returned : 1, 0
14:41:27 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -F
"C:\WINDOWS\sqlstp9.log" -I MSSQLSERVER -V 1 -M 0 -Q
"SQL_Latin1_General_CP1_CI_AS" -H 524590 -U sa -P
#####################
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=virtualserver1;UID=sa;PWD=;database =master
Configuring Server ...
EXEC sp_grantlogin N'BUILTIN\Administrators'
[Microsoft][ODBC SQL Server Driver][SQL Server]Granted login access to
'BUILTIN\Administrators'.
EXEC sp_addsrvrolemember N'BUILTIN\Administrators', 'sysadmin'
[Microsoft][ODBC SQL Server Driver][SQL Server]'BUILTIN\Administrators'
added to role 'sysadmin'.
update master.dbo.spt_server_info set attribute_value = @.@.version where
attribute_id = 2
EXEC sp_grantlogin N'TMC\bob'
[Microsoft][ODBC SQL Server Driver][SQL Server]Granted login access to
'TMC\bob'.
EXEC sp_addsrvrolemember N'TMC\bob', 'sysadmin'
[Microsoft][ODBC SQL Server Driver][SQL Server]'TMC\bob' added to role
'sysadmin'.
EXEC sp_addserver N'virtualserver1', local
[Microsoft][ODBC SQL Server Driver][SQL Server]Password changed.
EXEC sp_configure 'allow updates', 1
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If
DBCC printed error messages, contact your system administrator.
[Microsoft][ODBC SQL Server Driver][SQL Server]Configuration option 'allow
updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
reconfigure with override
update master.dbo.sysaltfiles set size=1024 where name=N'tempdev'
EXEC sp_configure 'allow updates', 0
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If
DBCC printed error messages, contact your system administrator.
[Microsoft][ODBC SQL Server Driver][SQL Server]Configuration option 'allow
updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
reconfigure with override
Disconnecting from Server ...
Stopping Service ...
SQL Server has been successfully configured!
################
14:42:22 Process Exit Code: (0)
14:42:22 End Action BuildServer
14:42:22 Begin Action SelfRegiser
14:42:22 DLLRegisterServer atl.dll: 0, 0x0
14:42:27 Manual DLLRegisterServer C:\Program Files\Common Files\Microsoft
Shared\Database Replication\Conflict Viewer\wzcnf.dll: 0, 0x0
14:42:27 Begin Action SelfRegisterOnCluster
14:42:27 End Action SelfRegisterOnCluster
14:42:27 Begin Action RegisterSvrReplFiles
14:42:27 End Action RegisterSvrReplFiles
14:42:27 Begin Action SelfRegisterCOMShared
14:42:27 End Action SelfRegisterCOMShared
14:42:27 End Action SelfRegister
14:42:27 Begin Action SetupRegistry:
14:42:27 SNMP service has been detected.
14:42:27 Begin Action RegWriteInstalledInstances:
14:42:27 End Action RegWriteInstalledInstances
14:42:27 Register this installation of SQL Server with MDAC
14:42:27 Completed registering this installation of SQL Server with MDAC
14:42:27 SetRegSecuritySQLAndAdmin for
Software\Microsoft\MSSQLServer\SQLServerAgent returned: 0, 0
14:42:27 SetRegSecuritySQLAndAdmin for
Software\Microsoft\MSSQLServer\Replication returned: 0, 0
14:42:27 SetRegSecuritySQLAndAdmin for
Software\Microsoft\MSSQLServer\Providers returned: 0, 0
14:42:27 SetRegSecuritySQLAndAdmin for Software\Microsoft\MSSQLServer\Setup
returned: 0, 0
14:42:27 SetRegSecuritySQLAndAdmin for
Software\Microsoft\MSSQLServer\Tracking returned: 0, 0
14:42:27 Updating SQL Licensing Control Panel information
14:42:27 Done updating SQL Licensing Control Panel information
14:42:27 SetRegSecuritySQLAndAdmin for
System\CurrentControlset\Services\MSSQLSERVER returned: 0, 0
14:42:27 SetRegSecuritySQLAndAdmin for Software\Microsoft\Windows
NT\CurrentVersion\Perflib returned: 0, 0
14:42:27 SetRegSecuritySQLAndAdmin for SOFTWARE\Clients\Mail returned: 0, 0
14:42:27 End Action SetupRegistry
14:42:27 Begin Action PostSetupRegistry:
14:42:27 C:\DOCUME~1\Username\LOCALS~1\Temp\SqlSetup\Bin\sc m.exe -Silent 1
-Action 7 -Service MSSQLSERVER -SvcStartType 1 -SvcAccount "TMC\bob" -SvcEPwd
14:42:27 Process Exit Code: (0)
14:42:27 C:\DOCUME~1\Username\LOCALS~1\Temp\SqlSetup\Bin\sc m.exe -Silent 1
-Action 5 -Service "SQLSERVERAGENT" -Dependencies MSSQLSERVER -ExePath
"C:\Program Files\Microsoft SQL Server\MSSQL\binn\sqlagent.exe" -SvcAccount
"TMC\bob" -SvcEPwd
14:42:33 Process Exit Code: (0)
14:42:33 SetupSQLExecSecurity returned: 0
14:42:33 PerfmonLoad returned: 0
14:42:33 C:\PROGRA~1\MICROS~1\80\Tools\Binn\dcomscm.exe /RegServer
14:42:33 Process Exit Code: (0)
14:42:33 MSSearch ApplicationName: SQLServer
14:42:33 C:\SQL2000_Ent\x86\FullText\ftsetup.exe SQLServer TMC\bob 1 0 1 0
14:42:33 C:\SQL2000_Ent\x86\FullText\ftsetup.exe SQLServer TMC\bob 1 0 1 0
14:42:33 Process Exit Code: (0)
14:42:33 FulltextSetup returned: 0
14:42:33 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe
-i -lcid 1033
14:42:33 Process Exit Code: (0)
14:42:33 End Action PostSetupRegistry
14:42:33 Begin Action SetupFolders:
14:42:33 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Enterprise Manager
14:42:33 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Enterprise Manager
14:42:33 Tracking\Shortcuts\Enterprise Manager
14:42:33 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Query Analyzer
14:42:33 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Query Analyzer
14:42:33 Tracking\Shortcuts\Query Analyzer
14:42:33 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Profiler
14:42:33 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Profiler
14:42:33 Tracking\Shortcuts\Profiler
14:42:33 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Client Network Utility
14:42:33 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Client Network
Utility
14:42:33 Tracking\Shortcuts\Client Network Utility
14:42:33 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Configure SQL XML Support in IIS
14:42:33 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Configure SQL XML
Support in IIS
14:42:33 Tracking\Shortcuts\Configure SQL XML Support in IIS
14:42:33 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Import and Export Data
14:42:33 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Import and Export
Data
14:42:33 Tracking\Shortcuts\Import and Export Data
14:42:33 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Service Manager
14:42:33 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Service Manager
14:42:33 Tracking\Shortcuts\Service Manager
14:42:33 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Server Network Utility
14:42:33 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Server Network
Utility
14:42:33 Tracking\Shortcuts\Server Network Utility
14:42:33 Microsoft SQL Server Folder refreshed.
14:42:33 End Action SetupFolders
14:42:33 Action CleanUpInstall:
14:42:33 Uninstall command: C:\WINDOWS\IsUninst.exe -f"C:\Program
Files\Microsoft SQL Server\MSSQL\Uninst.isu" -c"C:\Program Files\Microsoft
SQL Server\MSSQL\sqlsun.dll" -msql.mif i=MSSQLSERVER
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA4-5A21-11d2-9DAD-00C04F79D434}
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA7-5A21-11d2-9DAD-00C04F79D434}
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{6DC86044-0C71-11d3-9E18-00C04F79D434}
14:42:33 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDA8-5A21-11d2-9DAD-00C04F79D434} (1)
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA8-5A21-11d2-9DAD-00C04F79D434}
14:42:33 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDA9-5A21-11d2-9DAD-00C04F79D434} (1)
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA9-5A21-11d2-9DAD-00C04F79D434}
14:42:33 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAA-5A21-11d2-9DAD-00C04F79D434} (1)
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAA-5A21-11d2-9DAD-00C04F79D434}
14:42:33 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAB-5A21-11d2-9DAD-00C04F79D434} (1)
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAB-5A21-11d2-9DAD-00C04F79D434}
14:42:33 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAC-5A21-11d2-9DAD-00C04F79D434} (1)
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAC-5A21-11d2-9DAD-00C04F79D434}
14:42:33 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAD-5A21-11d2-9DAD-00C04F79D434} (1)
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAD-5A21-11d2-9DAD-00C04F79D434}
14:42:33 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDBE-5A21-11d2-9DAD-00C04F79D434} (1)
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
14:42:33 StatsGenerate returned: 2
14:42:33 StatsGenerate (0x0,0x1,0xf00000,0x0,1033,303,0x0,0x1000000a,0,0, 0
14:42:33 StatsGenerate -1,username)
14:42:33 Installation Succeeded
|||Figured out the problem. I had taken the MSDTC offline per a step-by-step
provided by a sql server website. This was incorrect in my situation. Once I
brought the MSDTC online the install was successful. Additionally to apply
SP3 I had to manually bring the sql virtual server online before running the
sp3 setup.
Thanks to everyone that helped!

New SQL Server 2000 worm?

Hi all.

My SQL Server 2000 SP4 installation running on Windows 2003 server (SP1, all patches current) has been infected TWICE by something that Sophos can't detect.

The symptoms are that an account called SQLsys is created on the machine and is made an administrator.

A service called "ApptoService spoolsrv" is created. An executable called syss.exe is also created in a few places. After infection the machine immediately starts attacking other computers on the network.

I had Windows Firewall running, with ports open for SQL server and Remote Desktop.

I ran the MBSA, it didn't find anything open.

I even ran the beta MS web tool for scanning, didn't detect any trojans.

I'm going to be restoring the machine (AGAIN), but I wish I knew what security hole is being found! Any ideas?
Please try changing your SA account password. Try a complicated password that has numbers, letters, and symbols in it. Also, do not allow your sql server to have inbound access to the internet. At the very least block port 1433 on your firewall.|||

Have you noticed this issue again after setting a strong SA password?

Thanks
Laurentiu

|||Try using Windows Defender beta which is a good one to catchup such trojans & spyware. Also check any spurious activity on SQL server by referring to data & log file usage with an audit trial.sql

New sql registration

I have a database that runs sql 7. Most of our workstations are running on a windows 98 platform, however, a few are running windows 2000. I am trying to set up a new sql registration in enterprise manager, but the connection is failing. All of the 98 machines are logging in with a sql user name, but I was told to log the 2000 machine as a NT server. If you can understand what my problem is, could you please advise me?
thanks :confused:What's the error you're getting? "Server doesn't exist or access is denied" or something else?|||It really isn't a error. IN the final box where you click finish, it says "SQL-unable to establish a connection, registration failed"
thanks
joyce|||You trying to register a 2000 server in 7.0 EM ?
Aint gonna happen !!!|||I THINK what they meant was that the Windoze-2000 machine should connect to your SQL 7.0 Server using NT authentication. If that is the case, In the "Connect Using" dialog you should use the NT Account instead of a SQL Login like you use on your Windoze-98 machines.

-PatP|||I THINK what they meant was that the Windoze-2000 machine should connect to your SQL 7.0 Server using NT authentication. If that is the case, In the "Connect Using" dialog you should use the NT Account instead of a SQL Login like you use on your Windoze-98 machines.

-PatP
Yes that is what I mean.
I did use the NT auth, but it still won't connect, any other ideas??
thanks
joyce|||My first guess would be that you need to enable NT Authentication (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_47u6.asp) for the NT login that the user of the Windoze-2000 machine will be using.

-PatP|||Well I thought it was enabled, is there a way to tell whether it is or not?|||Check in Enterprise Manglerto see if you can see the user's NT login in the list that is under the Server | Security | Logins.

-PatP|||ok, yes, the NT auth. is enabled. The user says NT user under type.|||You should check server properties for authentication. It's also not a dynamic property, which means Configured maybe different from Running (needs service bounced)

New Server, How to transfer data from old server?

I'm using SQLServer 2000 on Windows 2000 Server.
We have just purchased a new server. The new server will
have the EXACT same file structure, computer name, and
static IP address as the old server. (We DO NOT use
replication).
I want transfer my databases, DTSs, and Logins to the new
server from the old.
How do I so this?
Do I only need to transfer the User databases or must I
also transfer the Master, Model, Tempdb, and msdb system
databases?
Thanksmaster contains the logins which will be needed on the new server...
You could backup/restore master, and msdb...
You could could the copy database wizard to copy the rest...
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Brent Murphy" <brent.murphy@.us.schneider-electric.com> wrote in message
news:031d01c3af99$64620b70$a101280a@.phx.gbl...
> I'm using SQLServer 2000 on Windows 2000 Server.
> We have just purchased a new server. The new server will
> have the EXACT same file structure, computer name, and
> static IP address as the old server. (We DO NOT use
> replication).
> I want transfer my databases, DTSs, and Logins to the new
> server from the old.
> How do I so this?
> Do I only need to transfer the User databases or must I
> also transfer the Master, Model, Tempdb, and msdb system
> databases?
> Thanks
>|||Thanks Wayne.
So my Backed up Master DB will just overwrite whatever
Master DB is on the new server from the SQL Server 2000
install?
>--Original Message--
>master contains the logins which will be needed on the
new server...
>You could backup/restore master, and msdb...
>You could could the copy database wizard to copy the
rest...
>
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Computer Education Services Corporation (CESC),
Charlotte, NC
>www.computeredservices.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"Brent Murphy" <brent.murphy@.us.schneider-electric.com>
wrote in message
>news:031d01c3af99$64620b70$a101280a@.phx.gbl...
>> I'm using SQLServer 2000 on Windows 2000 Server.
>> We have just purchased a new server. The new server
will
>> have the EXACT same file structure, computer name, and
>> static IP address as the old server. (We DO NOT use
>> replication).
>> I want transfer my databases, DTSs, and Logins to the
new
>> server from the old.
>> How do I so this?
>> Do I only need to transfer the User databases or must I
>> also transfer the Master, Model, Tempdb, and msdb system
>> databases?
>> Thanks
>
>.
>|||Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Brent Murphy" <brent.murphy@.us.schneider-electric.com> wrote in message
news:031d01c3af99$64620b70$a101280a@.phx.gbl...
> I'm using SQLServer 2000 on Windows 2000 Server.
> We have just purchased a new server. The new server will
> have the EXACT same file structure, computer name, and
> static IP address as the old server. (We DO NOT use
> replication).
> I want transfer my databases, DTSs, and Logins to the new
> server from the old.
> How do I so this?
> Do I only need to transfer the User databases or must I
> also transfer the Master, Model, Tempdb, and msdb system
> databases?
> Thanks
>|||One approach that we have used:
Stop sql services (disable) on old SQL server, rename that
server and re-ip it to something temporary.
Name new server and IP it to it's production name/ip.
Install SQL 2000 on it maintaining the exact file
structure of the original.
Apply whatever SP's / hotfixes to get SQL / W2k versions
to match across old box / new box.
Stop all SQL services on new box. Rename the folders
where your mdf's and ldf's are stored.
Copy the folders with the mdf's and ldf's from the
original server to the new server.
Start the services and go into enterprise mgr. and make
sure that all of the DB's are online.
This process will transfer all db's, logins, etc. We have
used it many times. The key is to have the file structure
match exactly as you mentioned. (and sp's)
You will have to recreate any scheduled tasks / maint
plans using this approach. Or you can probably copy them
also by moving the whole mssql folders instead of just
those that contain the data/log files. We haven't tried
this, but it should work.
HTH, Chuck
>--Original Message--
>I'm using SQLServer 2000 on Windows 2000 Server.
>We have just purchased a new server. The new server will
>have the EXACT same file structure, computer name, and
>static IP address as the old server. (We DO NOT use
>replication).
>I want transfer my databases, DTSs, and Logins to the new
>server from the old.
>How do I so this?
>Do I only need to transfer the User databases or must I
>also transfer the Master, Model, Tempdb, and msdb system
>databases?
>Thanks
>.
>|||Thanks Chuck for the informative answer!
I have a question. You said "Stop all SQL services on new
box. Rename the folders where your mdf's and ldf's are
stored."
If I have the same file/folder structure on the new
server, why do I need to rename the folders? I didn't
under stand that part. Is it just so you don't copy over
whatever was put in the orignal folders from the install?
>--Original Message--
>One approach that we have used:
>Stop sql services (disable) on old SQL server, rename
that
>server and re-ip it to something temporary.
>Name new server and IP it to it's production name/ip.
>Install SQL 2000 on it maintaining the exact file
>structure of the original.
>Apply whatever SP's / hotfixes to get SQL / W2k versions
>to match across old box / new box.
>Stop all SQL services on new box. Rename the folders
>where your mdf's and ldf's are stored.
>Copy the folders with the mdf's and ldf's from the
>original server to the new server.
>Start the services and go into enterprise mgr. and make
>sure that all of the DB's are online.
>This process will transfer all db's, logins, etc. We
have
>used it many times. The key is to have the file
structure
>match exactly as you mentioned. (and sp's)
>You will have to recreate any scheduled tasks / maint
>plans using this approach. Or you can probably copy them
>also by moving the whole mssql folders instead of just
>those that contain the data/log files. We haven't tried
>this, but it should work.
>HTH, Chuck
>>--Original Message--
>>I'm using SQLServer 2000 on Windows 2000 Server.
>>We have just purchased a new server. The new server
will
>>have the EXACT same file structure, computer name, and
>>static IP address as the old server. (We DO NOT use
>>replication).
>>I want transfer my databases, DTSs, and Logins to the
new
>>server from the old.
>>How do I so this?
>>Do I only need to transfer the User databases or must I
>>also transfer the Master, Model, Tempdb, and msdb system
>>databases?
>>Thanks
>>.
>.
>|||Sorry took so long for me to get back.. You've probably already
figured this out, but the goal was to rename the data folders on the
new install in case anything went sideways when you copied the data
folders from the original install, so you can go back. Good luck!
Chuck
"Brent Murphy" <brent.murphy@.us.schneier-electric.com> wrote in message news:<0bc201c3b035$e1c4eb40$a101280a@.phx.gbl>...
> Thanks Chuck for the informative answer!
> I have a question. You said "Stop all SQL services on new
> box. Rename the folders where your mdf's and ldf's are
> stored."
> If I have the same file/folder structure on the new
> server, why do I need to rename the folders? I didn't
> under stand that part. Is it just so you don't copy over
> whatever was put in the orignal folders from the install?
>

New server registration error

Hi, I've just installed MSDE 2000 Release A on a Windows NT Server 4.0 w/SP6. I'm on a WinXP machine and I've installed the Enterprise Manager, and am trying to register a new server registration. However, I'm getting the error: Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection. I've made sure that both the client and server are using TCP/IP for the protocol list, and I've tried using the physical server's name and it's IP address to register, but keep getting the same error. Thanks for the help.How are you authentacating? Try a search before posting.
http://www.dbforums.com/t525129.html
or

http://search.msn.com/pass/results.asp?RS=CHECKED&FORM=MSNH&v=1&&q=Login+failed+for+user+%27sa%27.+&cp=1252|||I was trying to authenticate via SQL Authentication. I did try searching, and nothing I found seemed to pertain to my situation. But I fixed the problem, so if anyone wants to know, I used Windows authentication to register the server, then I right-clicked on the server, chose properties, and went to the security tab. In there, it was checked to use "Windows only" under the Authentication section. I changed it to "SQL Server and Windows", restarted the SQL service, deleted my Windows SQL registration. Then I was able to successfully register my SQL server using SQL Authentication!

New server name

I am tasked with bringing my Windows 2000 server which
runs SQL 7.0 into another domain as a member server. I
will have to change the name of my server also. Does this
affect SQL? I know the Services Manager refers to the
file server name and was wondering, after I change the
name, will SQL see this, or will I have to manually change
some things in SQL?Hi,
SQL 7.0 will not start after changing the Server name. You need to insert
the SQL Server CD and run setup.
This just updates the registry with the new server name and will not change
any databases.
After this start SQL server and login using Query Analyzer and execute below
commands,
sp_dropserver <old server name>
go
sp_addserver <newserver name>,local
Thanks
Hari
MCDBA
"Rick" <anonymous@.discussions.microsoft.com> wrote in message
news:0e6101c3a222$ddbface0$a501280a@.phx.gbl...
> I am tasked with bringing my Windows 2000 server which
> runs SQL 7.0 into another domain as a member server. I
> will have to change the name of my server also. Does this
> affect SQL? I know the Services Manager refers to the
> file server name and was wondering, after I change the
> name, will SQL see this, or will I have to manually change
> some things in SQL?|||SQL should recognize the new server name when you reboot or start and
stop sql services. I believe you should correct the sysservers system
table by manually running this...
sp_dropserver old_name
GO
sp_addserver new_name, local
GO
Billy|||For 7.0, you need to run setup as well.
--
Tibor Karaszi
"Billy" <bwood@.gibson.com> wrote in message
news:182d2236.0311031226.2ddcda98@.posting.google.com...
> SQL should recognize the new server name when you reboot or start and
> stop sql services. I believe you should correct the sysservers system
> table by manually running this...
> sp_dropserver old_name
> GO
> sp_addserver new_name, local
> GO
> Billy|||Thanks for the solid info Hari. Appreciate it.
>--Original Message--
>Hi,
>SQL 7.0 will not start after changing the Server name.
You need to insert
>the SQL Server CD and run setup.
>This just updates the registry with the new server name
and will not change
>any databases.
>After this start SQL server and login using Query
Analyzer and execute below
>commands,
>sp_dropserver <old server name>
>go
>sp_addserver <newserver name>,local
>Thanks
>Hari
>MCDBA
>
>
>"Rick" <anonymous@.discussions.microsoft.com> wrote in
message
>news:0e6101c3a222$ddbface0$a501280a@.phx.gbl...
>> I am tasked with bringing my Windows 2000 server which
>> runs SQL 7.0 into another domain as a member server. I
>> will have to change the name of my server also. Does
this
>> affect SQL? I know the Services Manager refers to the
>> file server name and was wondering, after I change the
>> name, will SQL see this, or will I have to manually
change
>> some things in SQL?
>
>.
>

New Server

Hello,
We have a dead Windows 2003 Server w/SQL2000. We have all SQL data in the
hard disk.
We will install new Windows 2003 Server w/SQL2005. How can we import old SQL
2000 data to SQL 2005?
ThanksHi,
Take a look at this
How to move databases between computers that are running SQL Server
http://support.microsoft.com/default.aspx/kb/314546/
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Newbie" wrote:

> Hello,
> We have a dead Windows 2003 Server w/SQL2000. We have all SQL data in the
> hard disk.
> We will install new Windows 2003 Server w/SQL2005. How can we import old S
QL
> 2000 data to SQL 2005?
> Thanks|||Thanks
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hi,
> Take a look at this
> How to move databases between computers that are running SQL Server
> http://support.microsoft.com/default.aspx/kb/314546/
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Newbie" wrote:
>

New Server

Hello,
We have a dead Windows 2003 Server w/SQL2000. We have all SQL data in the
hard disk.
We will install new Windows 2003 Server w/SQL2005. How can we import old SQL
2000 data to SQL 2005?
Thanks
Hi,
Take a look at this
How to move databases between computers that are running SQL Server
http://support.microsoft.com/default.aspx/kb/314546/
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Newbie" wrote:

> Hello,
> We have a dead Windows 2003 Server w/SQL2000. We have all SQL data in the
> hard disk.
> We will install new Windows 2003 Server w/SQL2005. How can we import old SQL
> 2000 data to SQL 2005?
> Thanks
|||Thanks
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hi,
> Take a look at this
> How to move databases between computers that are running SQL Server
> http://support.microsoft.com/default.aspx/kb/314546/
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Newbie" wrote:

New Server

Hello,
We have a dead Windows 2003 Server w/SQL2000. We have all SQL data in the
hard disk.
We will install new Windows 2003 Server w/SQL2005. How can we import old SQL
2000 data to SQL 2005?
ThanksHi,
Take a look at this
How to move databases between computers that are running SQL Server
http://support.microsoft.com/default.aspx/kb/314546/
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Newbie" wrote:
> Hello,
> We have a dead Windows 2003 Server w/SQL2000. We have all SQL data in the
> hard disk.
> We will install new Windows 2003 Server w/SQL2005. How can we import old SQL
> 2000 data to SQL 2005?
> Thanks|||Thanks
"Ben Nevarez" wrote:
> Hi,
> Take a look at this
> How to move databases between computers that are running SQL Server
> http://support.microsoft.com/default.aspx/kb/314546/
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Newbie" wrote:
> > Hello,
> >
> > We have a dead Windows 2003 Server w/SQL2000. We have all SQL data in the
> > hard disk.
> >
> > We will install new Windows 2003 Server w/SQL2005. How can we import old SQL
> > 2000 data to SQL 2005?
> >
> > Thanks