Consfued on how to handle memoey issue

Okay here is the question for all of brilliant guys. I have a server
loaded with windows 2003 Enterprise Edition with SP2 on it. I've 2
instanaces on sql 2000 sp3a running on them currently memory for the
box is 8 GB. Now the problem is, one of the instance is of ecommerce
database and that database is massive around 800-900 GB. currently,
it's running under memory pressure i mean sql server process is taking
around 1.8 GB but it's not going beyond that I know it's a problem
with 32-bit edition but we can't move our stuff to 64-bit right away.
I would like to know best way to tackle this problem. I mean what i
have to do to give in order to use more memory. Do i need to enable
AWE on both the instance and use /PAE switch or go beyond that and
use /3GB switch in boot.ini. Let me know.
Thanks,Hi
Which edition of SQL 2000 is this?
You can configure the maximum memory to use with sp_configure 'max server
memory' You can set values for each instance so they add up to 5 GB.
Have you enabled AWE on each instance.
John
"kulkarni.ninad@.gmail.com" wrote:
> Okay here is the question for all of brilliant guys. I have a server
> loaded with windows 2003 Enterprise Edition with SP2 on it. I've 2
> instanaces on sql 2000 sp3a running on them currently memory for the
> box is 8 GB. Now the problem is, one of the instance is of ecommerce
> database and that database is massive around 800-900 GB. currently,
> it's running under memory pressure i mean sql server process is taking
> around 1.8 GB but it's not going beyond that I know it's a problem
> with 32-bit edition but we can't move our stuff to 64-bit right away.
> I would like to know best way to tackle this problem. I mean what i
> have to do to give in order to use more memory. Do i need to enable
> AWE on both the instance and use /PAE switch or go beyond that and
> use /3GB switch in boot.ini. Let me know.
> Thanks,
>|||On Sep 27, 12:54 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> Which edition of SQL 2000 is this?
> You can configure the maximum memory to use with sp_configure 'max server
> memory' You can set values for each instance so they add up to 5 GB.
> Have you enabled AWE on each instance.
> John
>
> "kulkarni.ni...@.gmail.com" wrote:
> > Okay here is the question for all of brilliant guys. I have a server
> > loaded with windows 2003 Enterprise Edition with SP2 on it. I've 2
> > instanaces on sql 2000 sp3a running on them currently memory for the
> > box is 8 GB. Now the problem is, one of the instance is of ecommerce
> > database and that database is massive around 800-900 GB. currently,
> > it's running under memory pressure i mean sql server process is taking
> > around 1.8 GB but it's not going beyond that I know it's a problem
> > with 32-bit edition but we can't move our stuff to 64-bit right away.
> > I would like to know best way to tackle this problem. I mean what i
> > have to do to give in order to use more memory. Do i need to enable
> > AWE on both the instance and use /PAE switch or go beyond that and
> > use /3GB switch in boot.ini. Let me know.
> > Thanks,- Hide quoted text -
> - Show quoted text -
No we haven't enabled AWE actually and that's where I'm confused at
because in past, I have enabled AWE for single instance but haven't
done it for multiple instances.
Will it work if I enable AWE on both the instance of sql server? and
BTW, sql edition is Enterprise Edition.
Thanks,|||Hi
You should be able to enable AWE for both instances, but even if you enable
it for only one instance you should set the maximum memory for that instance
to avoid it grabbing all the memory.
John
"kulkarni.ninad@.gmail.com" wrote:
> On Sep 27, 12:54 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > Hi
> >
> > Which edition of SQL 2000 is this?
> >
> > You can configure the maximum memory to use with sp_configure 'max server
> > memory' You can set values for each instance so they add up to 5 GB.
> > Have you enabled AWE on each instance.
> >
> > John
> >
> >
> >
> > "kulkarni.ni...@.gmail.com" wrote:
> > > Okay here is the question for all of brilliant guys. I have a server
> > > loaded with windows 2003 Enterprise Edition with SP2 on it. I've 2
> > > instanaces on sql 2000 sp3a running on them currently memory for the
> > > box is 8 GB. Now the problem is, one of the instance is of ecommerce
> > > database and that database is massive around 800-900 GB. currently,
> > > it's running under memory pressure i mean sql server process is taking
> > > around 1.8 GB but it's not going beyond that I know it's a problem
> > > with 32-bit edition but we can't move our stuff to 64-bit right away.
> > > I would like to know best way to tackle this problem. I mean what i
> > > have to do to give in order to use more memory. Do i need to enable
> > > AWE on both the instance and use /PAE switch or go beyond that and
> > > use /3GB switch in boot.ini. Let me know.
> >
> > > Thanks,- Hide quoted text -
> >
> > - Show quoted text -
> No we haven't enabled AWE actually and that's where I'm confused at
> because in past, I have enabled AWE for single instance but haven't
> done it for multiple instances.
> Will it work if I enable AWE on both the instance of sql server? and
> BTW, sql edition is Enterprise Edition.
> Thanks,
>|||You do not need to add /3GB switch to the boot.ini file; however, you need
to add /PAE to be able to use 6GB of RAM over 8GB. Only enabling AWE won't
let you use 6GB of RAM. (You can use 6GB because Kernel Components and
Operating System use 2GB of RAM) And this process (enabling AWE and PAE)
needs a reboot of your server.
--
Ekrem Önsoy
<kulkarni.ninad@.gmail.com> wrote in message
news:1190914211.251116.224130@.57g2000hsv.googlegroups.com...
> On Sep 27, 12:54 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>> Hi
>> Which edition of SQL 2000 is this?
>> You can configure the maximum memory to use with sp_configure 'max server
>> memory' You can set values for each instance so they add up to 5 GB.
>> Have you enabled AWE on each instance.
>> John
>>
>> "kulkarni.ni...@.gmail.com" wrote:
>> > Okay here is the question for all of brilliant guys. I have a server
>> > loaded with windows 2003 Enterprise Edition with SP2 on it. I've 2
>> > instanaces on sql 2000 sp3a running on them currently memory for the
>> > box is 8 GB. Now the problem is, one of the instance is of ecommerce
>> > database and that database is massive around 800-900 GB. currently,
>> > it's running under memory pressure i mean sql server process is taking
>> > around 1.8 GB but it's not going beyond that I know it's a problem
>> > with 32-bit edition but we can't move our stuff to 64-bit right away.
>> > I would like to know best way to tackle this problem. I mean what i
>> > have to do to give in order to use more memory. Do i need to enable
>> > AWE on both the instance and use /PAE switch or go beyond that and
>> > use /3GB switch in boot.ini. Let me know.
>> > Thanks,- Hide quoted text -
>> - Show quoted text -
> No we haven't enabled AWE actually and that's where I'm confused at
> because in past, I have enabled AWE for single instance but haven't
> done it for multiple instances.
> Will it work if I enable AWE on both the instance of sql server? and
> BTW, sql edition is Enterprise Edition.
> Thanks,
>|||Hi
See http://www.sql-server-performance.com/tips/awe_memory_p1.aspx
John
"Ekrem Ã?nsoy" wrote:
> You do not need to add /3GB switch to the boot.ini file; however, you need
> to add /PAE to be able to use 6GB of RAM over 8GB. Only enabling AWE won't
> let you use 6GB of RAM. (You can use 6GB because Kernel Components and
> Operating System use 2GB of RAM) And this process (enabling AWE and PAE)
> needs a reboot of your server.
> --
> Ekrem nsoy
>
>
> <kulkarni.ninad@.gmail.com> wrote in message
> news:1190914211.251116.224130@.57g2000hsv.googlegroups.com...
> > On Sep 27, 12:54 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> >> Hi
> >>
> >> Which edition of SQL 2000 is this?
> >>
> >> You can configure the maximum memory to use with sp_configure 'max server
> >> memory' You can set values for each instance so they add up to 5 GB.
> >> Have you enabled AWE on each instance.
> >>
> >> John
> >>
> >>
> >>
> >> "kulkarni.ni...@.gmail.com" wrote:
> >> > Okay here is the question for all of brilliant guys. I have a server
> >> > loaded with windows 2003 Enterprise Edition with SP2 on it. I've 2
> >> > instanaces on sql 2000 sp3a running on them currently memory for the
> >> > box is 8 GB. Now the problem is, one of the instance is of ecommerce
> >> > database and that database is massive around 800-900 GB. currently,
> >> > it's running under memory pressure i mean sql server process is taking
> >> > around 1.8 GB but it's not going beyond that I know it's a problem
> >> > with 32-bit edition but we can't move our stuff to 64-bit right away.
> >> > I would like to know best way to tackle this problem. I mean what i
> >> > have to do to give in order to use more memory. Do i need to enable
> >> > AWE on both the instance and use /PAE switch or go beyond that and
> >> > use /3GB switch in boot.ini. Let me know.
> >>
> >> > Thanks,- Hide quoted text -
> >>
> >> - Show quoted text -
> >
> > No we haven't enabled AWE actually and that's where I'm confused at
> > because in past, I have enabled AWE for single instance but haven't
> > done it for multiple instances.
> > Will it work if I enable AWE on both the instance of sql server? and
> > BTW, sql edition is Enterprise Edition.
> >
> > Thanks,
> >
>|||Well, I'm not really sure of using /3GB all the time at least if it's really
unnecessary. I would not use it unless I really need that 1GB of RAM.
--
Ekrem Ã?nsoy
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:D2EE787C-CC99-4F84-8872-09B30278CD6A@.microsoft.com...
> Hi
> See http://www.sql-server-performance.com/tips/awe_memory_p1.aspx
> John
> "Ekrem Ã?nsoy" wrote:
>> You do not need to add /3GB switch to the boot.ini file; however, you
>> need
>> to add /PAE to be able to use 6GB of RAM over 8GB. Only enabling AWE
>> won't
>> let you use 6GB of RAM. (You can use 6GB because Kernel Components and
>> Operating System use 2GB of RAM) And this process (enabling AWE and PAE)
>> needs a reboot of your server.
>> --
>> Ekrem nsoy
>>
>>
>> <kulkarni.ninad@.gmail.com> wrote in message
>> news:1190914211.251116.224130@.57g2000hsv.googlegroups.com...
>> > On Sep 27, 12:54 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>> >> Hi
>> >>
>> >> Which edition of SQL 2000 is this?
>> >>
>> >> You can configure the maximum memory to use with sp_configure 'max
>> >> server
>> >> memory' You can set values for each instance so they add up to 5 GB.
>> >> Have you enabled AWE on each instance.
>> >>
>> >> John
>> >>
>> >>
>> >>
>> >> "kulkarni.ni...@.gmail.com" wrote:
>> >> > Okay here is the question for all of brilliant guys. I have a server
>> >> > loaded with windows 2003 Enterprise Edition with SP2 on it. I've 2
>> >> > instanaces on sql 2000 sp3a running on them currently memory for the
>> >> > box is 8 GB. Now the problem is, one of the instance is of ecommerce
>> >> > database and that database is massive around 800-900 GB. currently,
>> >> > it's running under memory pressure i mean sql server process is
>> >> > taking
>> >> > around 1.8 GB but it's not going beyond that I know it's a problem
>> >> > with 32-bit edition but we can't move our stuff to 64-bit right
>> >> > away.
>> >> > I would like to know best way to tackle this problem. I mean what i
>> >> > have to do to give in order to use more memory. Do i need to enable
>> >> > AWE on both the instance and use /PAE switch or go beyond that and
>> >> > use /3GB switch in boot.ini. Let me know.
>> >>
>> >> > Thanks,- Hide quoted text -
>> >>
>> >> - Show quoted text -
>> >
>> > No we haven't enabled AWE actually and that's where I'm confused at
>> > because in past, I have enabled AWE for single instance but haven't
>> > done it for multiple instances.
>> > Will it work if I enable AWE on both the instance of sql server? and
>> > BTW, sql edition is Enterprise Edition.
>> >
>> > Thanks,
>> >|||Hi
There should not be an issue using it as there is only a limited amount of
memory in the server. If the OP is seeing memory presure once AWE has been
enabled, then it is certainly something he should be doing.
John
"Ekrem Ã?nsoy" wrote:
> Well, I'm not really sure of using /3GB all the time at least if it's really
> unnecessary. I would not use it unless I really need that 1GB of RAM.
> --
> Ekrem Ã?nsoy
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:D2EE787C-CC99-4F84-8872-09B30278CD6A@.microsoft.com...
> > Hi
> >
> > See http://www.sql-server-performance.com/tips/awe_memory_p1.aspx
> >
> > John
> >
> > "Ekrem Ã?nsoy" wrote:
> >
> >> You do not need to add /3GB switch to the boot.ini file; however, you
> >> need
> >> to add /PAE to be able to use 6GB of RAM over 8GB. Only enabling AWE
> >> won't
> >> let you use 6GB of RAM. (You can use 6GB because Kernel Components and
> >> Operating System use 2GB of RAM) And this process (enabling AWE and PAE)
> >> needs a reboot of your server.
> >>
> >> --
> >> Ekrem nsoy
> >>
> >>
> >>
> >>
> >> <kulkarni.ninad@.gmail.com> wrote in message
> >> news:1190914211.251116.224130@.57g2000hsv.googlegroups.com...
> >> > On Sep 27, 12:54 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> >> >> Hi
> >> >>
> >> >> Which edition of SQL 2000 is this?
> >> >>
> >> >> You can configure the maximum memory to use with sp_configure 'max
> >> >> server
> >> >> memory' You can set values for each instance so they add up to 5 GB.
> >> >> Have you enabled AWE on each instance.
> >> >>
> >> >> John
> >> >>
> >> >>
> >> >>
> >> >> "kulkarni.ni...@.gmail.com" wrote:
> >> >> > Okay here is the question for all of brilliant guys. I have a server
> >> >> > loaded with windows 2003 Enterprise Edition with SP2 on it. I've 2
> >> >> > instanaces on sql 2000 sp3a running on them currently memory for the
> >> >> > box is 8 GB. Now the problem is, one of the instance is of ecommerce
> >> >> > database and that database is massive around 800-900 GB. currently,
> >> >> > it's running under memory pressure i mean sql server process is
> >> >> > taking
> >> >> > around 1.8 GB but it's not going beyond that I know it's a problem
> >> >> > with 32-bit edition but we can't move our stuff to 64-bit right
> >> >> > away.
> >> >> > I would like to know best way to tackle this problem. I mean what i
> >> >> > have to do to give in order to use more memory. Do i need to enable
> >> >> > AWE on both the instance and use /PAE switch or go beyond that and
> >> >> > use /3GB switch in boot.ini. Let me know.
> >> >>
> >> >> > Thanks,- Hide quoted text -
> >> >>
> >> >> - Show quoted text -
> >> >
> >> > No we haven't enabled AWE actually and that's where I'm confused at
> >> > because in past, I have enabled AWE for single instance but haven't
> >> > done it for multiple instances.
> >> > Will it work if I enable AWE on both the instance of sql server? and
> >> > BTW, sql edition is Enterprise Edition.
> >> >
> >> > Thanks,
> >> >
> >>
>

connectivity issues after SP2

Recently I upgraded a prod db server and since then users are experiencing
connectivity issues. The application errors out with :
Description [DBNETLIB] [ConnectionWrite (send()).] General network error.
Check your network documentation.
They try to ingore the error and sometimes work but not always.
No changes on the application side. The server is 64b Windows Server 2003 EE
with SQL 2005 EE 64b. installed. I upgraded both windows and sql to their SP2
..
I do have a test env. and there everithing went smoothly and no problems
have been reported.
No errors in the logs (both windows and sql server). A warning that network
card driver is outdated (Broadcom 1G). No network issues
The server is usually heavy loaded 8-5 and these issues start early
afternoon and once started happening they dont go away until users are done
for the day.
I am afraid of db corruption and all I can think about is to roll off the
service packs (both windows and sql)
Please help
Ellie
Can you show us connection string?
"Ellie" <Ellie@.discussions.microsoft.com> wrote in message
news:6C9C0F3B-C118-4B71-9F40-119D874EE783@.microsoft.com...
> Recently I upgraded a prod db server and since then users are experiencing
> connectivity issues. The application errors out with :
> Description [DBNETLIB] [ConnectionWrite (send()).] General network error.
> Check your network documentation.
> They try to ingore the error and sometimes work but not always.
> No changes on the application side. The server is 64b Windows Server 2003
> EE
> with SQL 2005 EE 64b. installed. I upgraded both windows and sql to their
> SP2
> .
> I do have a test env. and there everithing went smoothly and no problems
> have been reported.
> No errors in the logs (both windows and sql server). A warning that
> network
> card driver is outdated (Broadcom 1G). No network issues
> The server is usually heavy loaded 8-5 and these issues start early
> afternoon and once started happening they dont go away until users are
> done
> for the day.
> I am afraid of db corruption and all I can think about is to roll off the
> service packs (both windows and sql)
> Please help
|||> I am afraid of db corruption
No, I doubt it. You would be seeing different symptoms than connectivity
issues.
Have you considered paying attention to the network card driver issue? And
are you sure this isn't a network issue that happens to have started at or
around the same time you installed the service packs? Maybe there is some
process that is now running in the early afternoon that is hogging bandwidth
and making the network unreliable?

connectivity issues after SP2

Recently I upgraded a prod db server and since then users are experiencing
connectivity issues. The application errors out with :
Description [DBNETLIB] [ConnectionWrite (send()).] General network error.
Check your network documentation.
They try to ingore the error and sometimes work but not always.
No changes on the application side. The server is 64b Windows Server 2003 EE
with SQL 2005 EE 64b. installed. I upgraded both windows and sql to their SP2
.
I do have a test env. and there everithing went smoothly and no problems
have been reported.
No errors in the logs (both windows and sql server). A warning that network
card driver is outdated (Broadcom 1G). No network issues
The server is usually heavy loaded 8-5 and these issues start early
afternoon and once started happening they dont go away until users are done
for the day.
I am afraid of db corruption and all I can think about is to roll off the
service packs (both windows and sql)
Please helpEllie
Can you show us connection string?
"Ellie" <Ellie@.discussions.microsoft.com> wrote in message
news:6C9C0F3B-C118-4B71-9F40-119D874EE783@.microsoft.com...
> Recently I upgraded a prod db server and since then users are experiencing
> connectivity issues. The application errors out with :
> Description [DBNETLIB] [ConnectionWrite (send()).] General network error.
> Check your network documentation.
> They try to ingore the error and sometimes work but not always.
> No changes on the application side. The server is 64b Windows Server 2003
> EE
> with SQL 2005 EE 64b. installed. I upgraded both windows and sql to their
> SP2
> .
> I do have a test env. and there everithing went smoothly and no problems
> have been reported.
> No errors in the logs (both windows and sql server). A warning that
> network
> card driver is outdated (Broadcom 1G). No network issues
> The server is usually heavy loaded 8-5 and these issues start early
> afternoon and once started happening they dont go away until users are
> done
> for the day.
> I am afraid of db corruption and all I can think about is to roll off the
> service packs (both windows and sql)
> Please help|||> I am afraid of db corruption
No, I doubt it. You would be seeing different symptoms than connectivity
issues.
Have you considered paying attention to the network card driver issue? And
are you sure this isn't a network issue that happens to have started at or
around the same time you installed the service packs? Maybe there is some
process that is now running in the early afternoon that is hogging bandwidth
and making the network unreliable?

Connectivity issues

Hi,

I get the following error message trying to connect locally to sql server 2005 dev edition on xp sp2 machine.

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) (.Net SqlClient Data Provider)

I have enabled all protocols , the sql browser is running , sql agent and sql database engine not running. All other services like reporting etc are running.

The server is set up to run under local system account. Logging in as administrator, .

This server is installed as default instance . ( I do have sql exp and sql server 200 dev edition installed as named instances)

Beginning to pull my hair out.

Any help would be greatly appreciated.

Regards,

Well, you said the database engine is NOT running? From the looks of things that's what you're trying to connect to...I'll assume a typo maybe? The DB Engine service must be running if you're trying to connect to the SQL engine...

|||

Thank you Chad for the illuminating response.

The problem is precisely that the database engine will not start , I understand that the engine must running order for me to connect to a database , however I have made no mention of trying to connect to a database.

If you have any helpful suggestions I would really appreciate it.

Thank you

Andy

|||

Hi Andy...honestly, everything you wrote in your initial posting was indicating that you were having trouble trying to connect to the server...per your initial post:

"I get the following error message trying to connect locally to sql server 2005 dev edition on xp sp2 machine."

Then, the error message you posted indicates that you are indeed trying to connect to the server from an application:

"An error has occurred while establishing a connection to the server...."

And, it even describes a connection level provider (named pipes)...

So, given your original posting, it seems you are having trouble connecting to the instance, not getting it running. Myself and others would be more than happy to help you debug why you are having trouble getting the engine to start, but we'd need entirely different information.

If you'd like help with why the engine is not able to start, please post any error messages you notice in the application log, sql server error log, and system log related to the SQL Server instance, that's what we'd need to see to help you understand why the engine will not start.

On a final note, bear in mind that folks on the forums are trying to help you, not trying to insult you, and you'll always get more help if you treat myself and others with respect, not by being smart with us. You may notice that I am an administrator of these SQL forums, so please keep posts as civil as possible.

Regards

|||

HI Chad,

My apologies for coming across so curt , having re-read my response it does seem as though I was being rude , not my intention. Perhaps a bit of frustration creeping in, the problem is that my vocabulary and knowledge is lacking and expressing myself in a meaningful way is difficult and perhaps to some one with your knowledge, confusing.

If I am getting an error as described above when trying to get an instance started (i.e. the error is generated when I try and get the engine started) through Management Studio then I assume that error is relevant and that is what I will report on. Having read your second post it is now obvious that the error describes a connection problem rather than an issue regarding the instance running.( which obviously is as result of the engine not running.)

I checked the error log and found a network error which I googled , it seems as though if the via protocol is the culprit , having disabled this protocol the engine started .

The network error in the log:

TDSSNIClient initialization failed with error 0x7e, status code 0x60.

Thank you and my apologies once again.

|||

No worries, I definately understand frustation, we're all quite accustomed to that unfortunately. Glad you were able to get things working,

Regards,

sqlsql

Connectivity issue with SQL 2005 Developer Edition Named Instance

Hi,

I have installed one default and one named instance of SQL Server 2005 Dev. Editition SP2 on my server.

The Named service is configured to use Shared, NamedPipe and TCP (Port 4333).

There is no firewall on the machine. But still i am not able to connect to it form remote computer.

can any one help me with these. this is urgent.

Thanks.

KV

I found it. My SQL Browser service was running under domain account which was not working, i have configured it to run under NetworkService and it has started. sqlsql

Connectivity issue - SQLServer not listening on port 1433/ms-sql-s

Hi. I'm a SQL Server novice, so apologies if any of this sounds simple.

I am running Windows XP SP2, and have just installed SQLServer 2000. I
need another application to connect to SQLServer, and am specifying it
to do so via localhost:1433, but keep getting an error whenever I try
doing so saying it cannot connect to the database. A colleague of mine
has the exact same set up on his machine, and he can connect to SQL
Server fine. Running 'netstat -a' at the command line on his machine
reveals that the system is listening to port 1433/ms-sql-s. Running
netstat on my machine shows that the system is not listening to
1433/ms-sql-ms. I have checked in Network Config in SQLServer
Enterprise Manager, and TCP/IP is set to be using 1433.

To confirm this, my application can connect over the network to my
colleague's SQL Server. but he cannot connect over the network to mine.

So I'm pretty sure the issue is related to this 1433/ms-sql-s problem.
Does anyone know how to resolve this? Many thanks.I just installed SQL Server Service Pack 3, and the problem is now
resolved. Perhaps it was related to the Slammer worm.

Connection to SQL Server 2005

Hi all,
When I installed SPS 2003 , it installed MSDE as part of onstallation.
I also installed WSS SP 2 and SPS SP2 on it. I have SQL Server 2005
also installed on my machine.
How do I connect to this database for my WSS sites? How my sites in WSS
will be communicating to this sequal server?
Someone has suggeted that I should install SPS with SQLServer 2000 and
then upgrade it to SQL Server2005.I don't now why is it important to
install SQLServer 2000 and then upgrade it to 2005?
Is there any way that I can cope with the already made installations on
my machine?
Thanks
KahkashanDownload the WindowsSharePointServicesAdmin BOL from Microsoft, looks
into the section of 'Deployment Scenarios', it has very details how to
set up SPS to connect to a existing SQL Server (rather than use the
default WMSDE)
I followed the instruction and built a test SPS for our department, no
problem.
In the BOL, it only mention you need to have a SQL Server 2000 sp3 or
above to host the SPS databases. So you may need to check if they are
compatible with MSSQL 2005.
Mel

Connection to SQL Server 2005

Hi all,
When I installed SPS 2003 , it installed MSDE as part of onstallation.
I also installed WSS SP 2 and SPS SP2 on it. I have SQL Server 2005
also installed on my machine.
How do I connect to this database for my WSS sites? How my sites in WSS
will be communicating to this sequal server?
Someone has suggeted that I should install SPS with SQLServer 2000 and
then upgrade it to SQL Server2005.I don't now why is it important to
install SQLServer 2000 and then upgrade it to 2005?
Is there any way that I can cope with the already made installations on
my machine?
Thanks
KahkashanDownload the WindowsSharePointServicesAdmin BOL from Microsoft, looks
into the section of 'Deployment Scenarios', it has very details how to
set up SPS to connect to a existing SQL Server (rather than use the
default WMSDE)
I followed the instruction and built a test SPS for our department, no
problem.
In the BOL, it only mention you need to have a SQL Server 2000 sp3 or
above to host the SPS databases. So you may need to check if they are
compatible with MSSQL 2005.
Mel

Connection to SQL Server 2005

Hi all,
When I installed SPS 2003 , it installed MSDE as part of onstallation.
I also installed WSS SP 2 and SPS SP2 on it. I have SQL Server 2005
also installed on my machine.
How do I connect to this database for my WSS sites? How my sites in WSS
will be communicating to this sequal server?
Someone has suggeted that I should install SPS with SQLServer 2000 and
then upgrade it to SQL Server2005.I don't now why is it important to
install SQLServer 2000 and then upgrade it to 2005?
Is there any way that I can cope with the already made installations on
my machine?
Thanks
Kahkashan
Download the WindowsSharePointServicesAdmin BOL from Microsoft, looks
into the section of 'Deployment Scenarios', it has very details how to
set up SPS to connect to a existing SQL Server (rather than use the
default WMSDE)
I followed the instruction and built a test SPS for our department, no
problem.
In the BOL, it only mention you need to have a SQL Server 2000 sp3 or
above to host the SPS databases. So you may need to check if they are
compatible with MSSQL 2005.
Mel

Connection Problems

Hello,
I have a small workgroup of computers (4) all running windows xp sp2. One
of them is running msde2000. I can connect to a named instance of sql server
but can not connect to the default instance. I am using osql and using
trusted connection. I am not sure what other information is needed so
please do not hesitate to ask! I am really pulling my hair out on this one!
Any help would be greatly appreciated.
Hello,
Did you activated TCPIP network protocol for this default instance (verify
in the error.log for the instance)?
Hope this will help.
Philippe RUELLO
DBA MSSQL
"Michael O'S" <mroresolutions@.woh.rr.com> a crit dans le message de news:
NhMxd.3864$mA3.1811@.fe2.columbus.rr.com...
> Hello,
> I have a small workgroup of computers (4) all running windows xp sp2. One
> of them is running msde2000. I can connect to a named instance of sql
> server but can not connect to the default instance. I am using osql and
> using trusted connection. I am not sure what other information is needed
> so please do not hesitate to ask! I am really pulling my hair out on this
> one!
> Any help would be greatly appreciated.
>
|||Are you sure there is a default instance? If it's just MSDE 2000, there
usually is not a default instance. It installs to a named instance by
default. Look in Administrative Tools/Services for all SQL Server services.
See if you have any running besides the named instance.
"Philippe RUELLO" <pruello@.tibco.fr> wrote in message
news:uReN1wF7EHA.2124@.TK2MSFTNGP15.phx.gbl...
> Hello,
> Did you activated TCPIP network protocol for this default instance
(verify[vbcol=seagreen]
> in the error.log for the instance)?
> Hope this will help.
> --
> Philippe RUELLO
> DBA MSSQL
> "Michael O'S" <mroresolutions@.woh.rr.com> a crit dans le message de news:
> NhMxd.3864$mA3.1811@.fe2.columbus.rr.com...
One[vbcol=seagreen]
needed[vbcol=seagreen]
this
>
|||Thank you for your input! I did check tcpip settings and all were good. I
did however find in the server logs that some intances (including the
default) were not listening or failing to bind to port 1433.
I ended up removing msde instance that I could not connect to and
reinstalling making sure to use the DISABLENETWORKPROTOCOLS=0 parameter.
After I did this, I could see all instances of msde on any computer from any
computer in my workgroup.
Good Luck!
"Michael O'S" wrote:

> Hello,
> I have a small workgroup of computers (4) all running windows xp sp2. One
> of them is running msde2000. I can connect to a named instance of sql server
> but can not connect to the default instance. I am using osql and using
> trusted connection. I am not sure what other information is needed so
> please do not hesitate to ask! I am really pulling my hair out on this one!
> Any help would be greatly appreciated.
>
>

Connection problem with WinXP SP2

We have several loptops that run Windows XP and have SQL
Server databases, which we access through a Java
application. After WinXP Service Pack 2 was installed,
none of the laptops can connect to the database. We have
tried opening port 1433 for TCP/IP and port 445 for Named
Pipes; still no connection. If we uninstall SP2, the
problem disappears. Has anyone else seen this behavior, or
have any ideas of other approaches to making the
connection with SP2 on the laptop?
apart from 1433, you need to open UDP port 1434 also for SQL Server.
John Wilheim wrote:
> We have several loptops that run Windows XP and have SQL
> Server databases, which we access through a Java
> application. After WinXP Service Pack 2 was installed,
> none of the laptops can connect to the database. We have
> tried opening port 1433 for TCP/IP and port 445 for Named
> Pipes; still no connection. If we uninstall SP2, the
> problem disappears. Has anyone else seen this behavior, or
> have any ideas of other approaches to making the
> connection with SP2 on the laptop?

Connection problem with WinXP SP2

We have several loptops that run Windows XP and have SQL
Server databases, which we access through a Java
application. After WinXP Service Pack 2 was installed,
none of the laptops can connect to the database. We have
tried opening port 1433 for TCP/IP and port 445 for Named
Pipes; still no connection. If we uninstall SP2, the
problem disappears. Has anyone else seen this behavior, or
have any ideas of other approaches to making the
connection with SP2 on the laptop?apart from 1433, you need to open UDP port 1434 also for SQL Server.
John Wilheim wrote:
> We have several loptops that run Windows XP and have SQL
> Server databases, which we access through a Java
> application. After WinXP Service Pack 2 was installed,
> none of the laptops can connect to the database. We have
> tried opening port 1433 for TCP/IP and port 445 for Named
> Pipes; still no connection. If we uninstall SP2, the
> problem disappears. Has anyone else seen this behavior, or
> have any ideas of other approaches to making the
> connection with SP2 on the laptop?