How to enable TCP/IP connectons to SqlServer

How to enable remote connections on TCP/IP?

I have just installed for first time SqlServer 2000,
and cannot connect from other host via ODBC.
I give hostname or address but it does not connect.
I checked on my firewall that there is no listenning socket
on port 1433 nor 1440 on sqlserver host.

I can only connect using "(local)" server in ODBC on sqlserver host.

Regards,
Mark"netx" <user72wytnij@.go2.pl> wrote in message
news:42302557$0$3224$f69f905@.mamut2.aster.pl...
> How to enable remote connections on TCP/IP?
> I have just installed for first time SqlServer 2000,
> and cannot connect from other host via ODBC.
> I give hostname or address but it does not connect.
> I checked on my firewall that there is no listenning socket
> on port 1433 nor 1440 on sqlserver host.
> I can only connect using "(local)" server in ODBC on sqlserver host.

start->programs->Microsoft SQL Server->Client Network Utility

then click on TCP/IP in right panel and press 'enable'button', click on
'applay', 'ok' then restart SQL server

Regards,
Fibre Optic|||Fibre Optic (fibre_optic@.go2.pl) writes:
> "netx" <user72wytnij@.go2.pl> wrote in message
> news:42302557$0$3224$f69f905@.mamut2.aster.pl...
>> How to enable remote connections on TCP/IP?
>>
>> I have just installed for first time SqlServer 2000,
>> and cannot connect from other host via ODBC.
>> I give hostname or address but it does not connect.
>> I checked on my firewall that there is no listenning socket
>> on port 1433 nor 1440 on sqlserver host.
>>
>> I can only connect using "(local)" server in ODBC on sqlserver host.
>
> start->programs->Microsoft SQL Server->Client Network Utility
> then click on TCP/IP in right panel and press 'enable'button', click on
> 'applay', 'ok' then restart SQL server

You probably mean the Server Network Utility.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

How to enable SMO and SQL-DMO

When I installed SqlServer 2005 SP1, a warning message stated that I need to
install Hotfix 2047 or higher. I searched MSDN website and found Cumulative
hotfix package (buld 2153) for SQL Server 2005.
If I understand correctly there are 6 different hotfixes that must be
applied in a particular sequence and I must enable something called Server
Management Object (SMO), and SQL Server Distributed Management Object
(SQL-DMO) before installing the hotfix package.
"You must enable the SQL Server Management Object (SMO) and SQL Server
Distributed Management Object (SQL-DMO) extended stored procedures before
you install the hotfix package. For more information about the SMO/DMO XPs
option, see SQL Server 2005 Books Online."
I have searched Books Online extensively and found nothing specific about
enablling SMO and SQL-DMO. Can someone please give me the short version of
how to do this?
Thanks,
KeithThey are both enabled by default. If you want to verify, use sp_configure.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"keith" <kbrickey@.dslextreme.com> wrote in message news:OPxx0cUTHHA.480@.TK2MSFTNGP02.phx.gbl
..
> When I installed SqlServer 2005 SP1, a warning message stated that I need
to
> install Hotfix 2047 or higher. I searched MSDN website and found Cumulativ
e
> hotfix package (buld 2153) for SQL Server 2005.
> If I understand correctly there are 6 different hotfixes that must be
> applied in a particular sequence and I must enable something called Server
> Management Object (SMO), and SQL Server Distributed Management Object
> (SQL-DMO) before installing the hotfix package.
> "You must enable the SQL Server Management Object (SMO) and SQL Server
> Distributed Management Object (SQL-DMO) extended stored procedures before
> you install the hotfix package. For more information about the SMO/DMO XPs
> option, see SQL Server 2005 Books Online."
> I have searched Books Online extensively and found nothing specific about
> enablling SMO and SQL-DMO. Can someone please give me the short version of
> how to do this?
> Thanks,
> Keith
>sql

How to enable SMO and SQL-DMO

When I installed SqlServer 2005 SP1, a warning message stated that I need to
install Hotfix 2047 or higher. I searched MSDN website and found Cumulative
hotfix package (buld 2153) for SQL Server 2005.
If I understand correctly there are 6 different hotfixes that must be
applied in a particular sequence and I must enable something called Server
Management Object (SMO), and SQL Server Distributed Management Object
(SQL-DMO) before installing the hotfix package.
"You must enable the SQL Server Management Object (SMO) and SQL Server
Distributed Management Object (SQL-DMO) extended stored procedures before
you install the hotfix package. For more information about the SMO/DMO XPs
option, see SQL Server 2005 Books Online."
I have searched Books Online extensively and found nothing specific about
enablling SMO and SQL-DMO. Can someone please give me the short version of
how to do this?
Thanks,
KeithThey are both enabled by default. If you want to verify, use sp_configure.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"keith" <kbrickey@.dslextreme.com> wrote in message news:OPxx0cUTHHA.480@.TK2MSFTNGP02.phx.gbl...
> When I installed SqlServer 2005 SP1, a warning message stated that I need to
> install Hotfix 2047 or higher. I searched MSDN website and found Cumulative
> hotfix package (buld 2153) for SQL Server 2005.
> If I understand correctly there are 6 different hotfixes that must be
> applied in a particular sequence and I must enable something called Server
> Management Object (SMO), and SQL Server Distributed Management Object
> (SQL-DMO) before installing the hotfix package.
> "You must enable the SQL Server Management Object (SMO) and SQL Server
> Distributed Management Object (SQL-DMO) extended stored procedures before
> you install the hotfix package. For more information about the SMO/DMO XPs
> option, see SQL Server 2005 Books Online."
> I have searched Books Online extensively and found nothing specific about
> enablling SMO and SQL-DMO. Can someone please give me the short version of
> how to do this?
> Thanks,
> Keith
>

How to Enable Email Subscriptions

We recently installed email capability on the server where the Report Server
lives. What do we have to do to enable subscriptions to be emailed to people?
When I go to set up a subscription it doesn't list "Email" as a report
delivery mechanism. Do I have to change something in the RS config (if
so...where and what?) or do we just need to restart Reporting Services on
that server and it will know that email is enabled?
Thanks.You will need to go into the Reporting Services Configuration Manager and set
up your Email settings.
For more information you can go to this link:
http://msdn2.microsoft.com/en-us/library/ms345234.aspx
--
~lb
"Lucky Horseshoe" wrote:
> We recently installed email capability on the server where the Report Server
> lives. What do we have to do to enable subscriptions to be emailed to people?
> When I go to set up a subscription it doesn't list "Email" as a report
> delivery mechanism. Do I have to change something in the RS config (if
> so...where and what?) or do we just need to restart Reporting Services on
> that server and it will know that email is enabled?
> Thanks.

How to Enable CLR Integration in SQL Server Express and Create SQLCLR Project in VB 2005 Express

Hi all,

In my SQL Server Express (that is installed in my Windows XP Pro PC), SQL Server 2005 Network Configuration has Protocols for SQLEXPRESS. I tried to do "Enabling CLR Integration" in my SQL Server Express: (1) If I clicked on "Surface Area Configuration for Services and Connections", I got an error "An exception occurred in SMO while trying to manage a service, (Microsoft.SqlServer.Smo) Additional information: Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) The operation could not be completed. (WinMgmt). (2) If I clicked on "Surface Area Configuration for Features, I got a different error "Computer localhost does not exist on the network, or the computer cannot be configured remotely. Verify that the remote computer has the required computer has the required Windows Management Instrumentation components and then try again. (SQLSAC) Additional Information: An exception occurred in SMO while trying to manage a service. (Microsoft.SqlServer.Smo). Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) The operation could not be completed. (WinMgmt). Please help and tell me how I should do to get "Enabling CLR Integration" in my SQL Server Express done and how I can create SQLCLR Project in VB 2005 Express.

Thanks in advance,

Scott Chang

Normally you would enable the CLR using the Surface Area Configuration Tool, but it appears that something is wrong with SMO on your computer. I don't know much about how to fix SMO and SAC, so you should ask some questions about how to get these tools working over in the General Tools forum. Having SMO broken will impact other tools that you might want to use, so this is relatively important.

In the mean time, you can configure CLR manually using TSQL by running the following query in management studio or using SQLCmd:

Code Snippet

sp_configure 'clr enabled', 1

RECONFIGURE

Check out the topic on server configuration in BOL for more informaiton.

Mike

|||

I think the SMO problem is related to a WMI problem on your machine, it would be interesting if you could post the error messages to see if the message correlate with the assumptions that this is based on the WMI part of SMO.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Hi Jens and Mike, Thanks for your responses.

I guess my SQL Express 9.0.1399 is too old to get the CLR Integration. I am thinking to delete this 2-year old SQL Express in my PC and download and install the Microsoft Advanced SQL Erxpress (with some SP) for "Enabling CLR Integration". Is it a right thing for me to do? Please respond.

Thanks,

Scott Chang

|||

Hi Scott,

I'm curious as to how you've come to this conclusion? Did you try running the command I suggested to enable the CLR?

All versions of SQL Express 2005, including the one you list, support integrated CLR. The T-SQL command I suggested should enable the CLR. I believe it is a best practice to always run the latest service pack, which is SP2 right now, but the SP-level has nothing to do with CLR support.

If Jen's suggestion about a WMI configuration problem causing your issues with SAC, upgrading or re-installing will not fix that problem either since WMI is a Windows component. If it's not configured correctly on your computer, SQL can't do anything about it, you have to fix WMI. I would suggest posting the error you are getting as Jen's suggested to see if ayone has heard of your specific message.

Mike

|||

Hi Mike and Jens, Thank you both for your responses.

I have tried to understand what you said for 10 days. I thought I already presented the error messages in my first posting. Sorry, I am new in WMI, SMO and CLRSAC and I am completely lost now. I want to tell you that my SQL Server Express is in my personal PC that is a stand-alone Windows XP Pro PC without any Network/LAN system. I think I did not know how to configure my SQL Server Express correctly when I installed it 2 years ago. Please tell me how I can get the specific error messages Jens asked for.

Thanks again,

Scott Chang

|||

Hi Scott,

First, I want to make sure that you understand tha WMI is not part of SQL Server, it is a Windows component that many different systems rely on and use. As I said, it seems that you are getting SMO errors when you try to run the Surface Area Configuration Tool; you should probably go and post this question in the General Tools forum as that is the group that deals with SAC.

If the problem is really related to WMI, it could be that your WMI Repository is corrupt, and you could try rebuilding it. When you start messing with the sub-systems of Windows, it's always possible that you could make things worse if you do stuff wrong. If you're concerned about this, you should look for help from the right sources, General Tools for SAC and the Windows Group for help with WMI.

If you're bold, you could give the repository rebuild a try, one set of instructions is posted at http://www.nucleustechnologies.com/Repair-WMI-Services.php.

Mike

How to Enable CLR Integration in SQL Server Express and Create SQLCLR Project in VB 2005 Express

Hi all,

In my SQL Server Express (that is installed in my Windows XP Pro PC), SQL Server 2005 Network Configuration has Protocols for SQLEXPRESS. I tried to do "Enabling CLR Integration" in my SQL Server Express: (1) If I clicked on "Surface Area Configuration for Services and Connections", I got an error "An exception occurred in SMO while trying to manage a service, (Microsoft.SqlServer.Smo) Additional information: Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) The operation could not be completed. (WinMgmt). (2) If I clicked on "Surface Area Configuration for Features, I got a different error "Computer localhost does not exist on the network, or the computer cannot be configured remotely. Verify that the remote computer has the required computer has the required Windows Management Instrumentation components and then try again. (SQLSAC) Additional Information: An exception occurred in SMO while trying to manage a service. (Microsoft.SqlServer.Smo). Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) The operation could not be completed. (WinMgmt). Please help and tell me how I should do to get "Enabling CLR Integration" in my SQL Server Express done and how I can create SQLCLR Project in VB 2005 Express.

Thanks in advance,

Scott Chang

Normally you would enable the CLR using the Surface Area Configuration Tool, but it appears that something is wrong with SMO on your computer. I don't know much about how to fix SMO and SAC, so you should ask some questions about how to get these tools working over in the General Tools forum. Having SMO broken will impact other tools that you might want to use, so this is relatively important.

In the mean time, you can configure CLR manually using TSQL by running the following query in management studio or using SQLCmd:

Code Snippet

sp_configure 'clr enabled', 1

RECONFIGURE

Check out the topic on server configuration in BOL for more informaiton.

Mike

|||

I think the SMO problem is related to a WMI problem on your machine, it would be interesting if you could post the error messages to see if the message correlate with the assumptions that this is based on the WMI part of SMO.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Hi Jens and Mike, Thanks for your responses.

I guess my SQL Express 9.0.1399 is too old to get the CLR Integration. I am thinking to delete this 2-year old SQL Express in my PC and download and install the Microsoft Advanced SQL Erxpress (with some SP) for "Enabling CLR Integration". Is it a right thing for me to do? Please respond.

Thanks,

Scott Chang

|||

Hi Scott,

I'm curious as to how you've come to this conclusion? Did you try running the command I suggested to enable the CLR?

All versions of SQL Express 2005, including the one you list, support integrated CLR. The T-SQL command I suggested should enable the CLR. I believe it is a best practice to always run the latest service pack, which is SP2 right now, but the SP-level has nothing to do with CLR support.

If Jen's suggestion about a WMI configuration problem causing your issues with SAC, upgrading or re-installing will not fix that problem either since WMI is a Windows component. If it's not configured correctly on your computer, SQL can't do anything about it, you have to fix WMI. I would suggest posting the error you are getting as Jen's suggested to see if ayone has heard of your specific message.

Mike

|||

Hi Mike and Jens, Thank you both for your responses.

I have tried to understand what you said for 10 days. I thought I already presented the error messages in my first posting. Sorry, I am new in WMI, SMO and CLRSAC and I am completely lost now. I want to tell you that my SQL Server Express is in my personal PC that is a stand-alone Windows XP Pro PC without any Network/LAN system. I think I did not know how to configure my SQL Server Express correctly when I installed it 2 years ago. Please tell me how I can get the specific error messages Jens asked for.

Thanks again,

Scott Chang

|||

Hi Scott,

First, I want to make sure that you understand tha WMI is not part of SQL Server, it is a Windows component that many different systems rely on and use. As I said, it seems that you are getting SMO errors when you try to run the Surface Area Configuration Tool; you should probably go and post this question in the General Tools forum as that is the group that deals with SAC.

If the problem is really related to WMI, it could be that your WMI Repository is corrupt, and you could try rebuilding it. When you start messing with the sub-systems of Windows, it's always possible that you could make things worse if you do stuff wrong. If you're concerned about this, you should look for help from the right sources, General Tools for SAC and the Windows Group for help with WMI.

If you're bold, you could give the repository rebuild a try, one set of instructions is posted at http://www.nucleustechnologies.com/Repair-WMI-Services.php.

Mike

How to Enable CLR Integration in SQL Server Express and Create SQLCLR Project in VB 2005 Express

Hi all,

In my SQL Server Express (that is installed in my Windows XP Pro PC), SQL Server 2005 Network Configuration has Protocols for SQLEXPRESS. I tried to do "Enabling CLR Integration" in my SQL Server Express: (1) If I clicked on "Surface Area Configuration for Services and Connections", I got an error "An exception occurred in SMO while trying to manage a service, (Microsoft.SqlServer.Smo) Additional information: Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) The operation could not be completed. (WinMgmt). (2) If I clicked on "Surface Area Configuration for Features, I got a different error "Computer localhost does not exist on the network, or the computer cannot be configured remotely. Verify that the remote computer has the required computer has the required Windows Management Instrumentation components and then try again. (SQLSAC) Additional Information: An exception occurred in SMO while trying to manage a service. (Microsoft.SqlServer.Smo). Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) The operation could not be completed. (WinMgmt). Please help and tell me how I should do to get "Enabling CLR Integration" in my SQL Server Express done and how I can create SQLCLR Project in VB 2005 Express.

Thanks in advance,

Scott Chang

Normally you would enable the CLR using the Surface Area Configuration Tool, but it appears that something is wrong with SMO on your computer. I don't know much about how to fix SMO and SAC, so you should ask some questions about how to get these tools working over in the General Tools forum. Having SMO broken will impact other tools that you might want to use, so this is relatively important.

In the mean time, you can configure CLR manually using TSQL by running the following query in management studio or using SQLCmd:

Code Snippet

sp_configure 'clr enabled', 1

RECONFIGURE

Check out the topic on server configuration in BOL for more informaiton.

Mike

|||

I think the SMO problem is related to a WMI problem on your machine, it would be interesting if you could post the error messages to see if the message correlate with the assumptions that this is based on the WMI part of SMO.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Hi Jens and Mike, Thanks for your responses.

I guess my SQL Express 9.0.1399 is too old to get the CLR Integration. I am thinking to delete this 2-year old SQL Express in my PC and download and install the Microsoft Advanced SQL Erxpress (with some SP) for "Enabling CLR Integration". Is it a right thing for me to do? Please respond.

Thanks,

Scott Chang

|||

Hi Scott,

I'm curious as to how you've come to this conclusion? Did you try running the command I suggested to enable the CLR?

All versions of SQL Express 2005, including the one you list, support integrated CLR. The T-SQL command I suggested should enable the CLR. I believe it is a best practice to always run the latest service pack, which is SP2 right now, but the SP-level has nothing to do with CLR support.

If Jen's suggestion about a WMI configuration problem causing your issues with SAC, upgrading or re-installing will not fix that problem either since WMI is a Windows component. If it's not configured correctly on your computer, SQL can't do anything about it, you have to fix WMI. I would suggest posting the error you are getting as Jen's suggested to see if ayone has heard of your specific message.

Mike

|||

Hi Mike and Jens, Thank you both for your responses.

I have tried to understand what you said for 10 days. I thought I already presented the error messages in my first posting. Sorry, I am new in WMI, SMO and CLRSAC and I am completely lost now. I want to tell you that my SQL Server Express is in my personal PC that is a stand-alone Windows XP Pro PC without any Network/LAN system. I think I did not know how to configure my SQL Server Express correctly when I installed it 2 years ago. Please tell me how I can get the specific error messages Jens asked for.

Thanks again,

Scott Chang

|||

Hi Scott,

First, I want to make sure that you understand tha WMI is not part of SQL Server, it is a Windows component that many different systems rely on and use. As I said, it seems that you are getting SMO errors when you try to run the Surface Area Configuration Tool; you should probably go and post this question in the General Tools forum as that is the group that deals with SAC.

If the problem is really related to WMI, it could be that your WMI Repository is corrupt, and you could try rebuilding it. When you start messing with the sub-systems of Windows, it's always possible that you could make things worse if you do stuff wrong. If you're concerned about this, you should look for help from the right sources, General Tools for SAC and the Windows Group for help with WMI.

If you're bold, you could give the repository rebuild a try, one set of instructions is posted at http://www.nucleustechnologies.com/Repair-WMI-Services.php.

Mike

sql

How to Enable CLR Integration in SQL Server Express and Create SQLCLR Project in VB 2005 Express

Hi all,

In my SQL Server Express (that is installed in my Windows XP Pro PC), SQL Server 2005 Network Configuration has Protocols for SQLEXPRESS. I tried to do "Enabling CLR Integration" in my SQL Server Express: (1) If I clicked on "Surface Area Configuration for Services and Connections", I got an error "An exception occurred in SMO while trying to manage a service, (Microsoft.SqlServer.Smo) Additional information: Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) The operation could not be completed. (WinMgmt). (2) If I clicked on "Surface Area Configuration for Features, I got a different error "Computer localhost does not exist on the network, or the computer cannot be configured remotely. Verify that the remote computer has the required computer has the required Windows Management Instrumentation components and then try again. (SQLSAC) Additional Information: An exception occurred in SMO while trying to manage a service. (Microsoft.SqlServer.Smo). Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) The operation could not be completed. (WinMgmt). Please help and tell me how I should do to get "Enabling CLR Integration" in my SQL Server Express done and how I can create SQLCLR Project in VB 2005 Express.

Thanks in advance,

Scott Chang

Normally you would enable the CLR using the Surface Area Configuration Tool, but it appears that something is wrong with SMO on your computer. I don't know much about how to fix SMO and SAC, so you should ask some questions about how to get these tools working over in the General Tools forum. Having SMO broken will impact other tools that you might want to use, so this is relatively important.

In the mean time, you can configure CLR manually using TSQL by running the following query in management studio or using SQLCmd:

Code Snippet

sp_configure 'clr enabled', 1

RECONFIGURE

Check out the topic on server configuration in BOL for more informaiton.

Mike

|||

I think the SMO problem is related to a WMI problem on your machine, it would be interesting if you could post the error messages to see if the message correlate with the assumptions that this is based on the WMI part of SMO.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Hi Jens and Mike, Thanks for your responses.

I guess my SQL Express 9.0.1399 is too old to get the CLR Integration. I am thinking to delete this 2-year old SQL Express in my PC and download and install the Microsoft Advanced SQL Erxpress (with some SP) for "Enabling CLR Integration". Is it a right thing for me to do? Please respond.

Thanks,

Scott Chang

|||

Hi Scott,

I'm curious as to how you've come to this conclusion? Did you try running the command I suggested to enable the CLR?

All versions of SQL Express 2005, including the one you list, support integrated CLR. The T-SQL command I suggested should enable the CLR. I believe it is a best practice to always run the latest service pack, which is SP2 right now, but the SP-level has nothing to do with CLR support.

If Jen's suggestion about a WMI configuration problem causing your issues with SAC, upgrading or re-installing will not fix that problem either since WMI is a Windows component. If it's not configured correctly on your computer, SQL can't do anything about it, you have to fix WMI. I would suggest posting the error you are getting as Jen's suggested to see if ayone has heard of your specific message.

Mike

|||

Hi Mike and Jens, Thank you both for your responses.

I have tried to understand what you said for 10 days. I thought I already presented the error messages in my first posting. Sorry, I am new in WMI, SMO and CLRSAC and I am completely lost now. I want to tell you that my SQL Server Express is in my personal PC that is a stand-alone Windows XP Pro PC without any Network/LAN system. I think I did not know how to configure my SQL Server Express correctly when I installed it 2 years ago. Please tell me how I can get the specific error messages Jens asked for.

Thanks again,

Scott Chang

|||

Hi Scott,

First, I want to make sure that you understand tha WMI is not part of SQL Server, it is a Windows component that many different systems rely on and use. As I said, it seems that you are getting SMO errors when you try to run the Surface Area Configuration Tool; you should probably go and post this question in the General Tools forum as that is the group that deals with SAC.

If the problem is really related to WMI, it could be that your WMI Repository is corrupt, and you could try rebuilding it. When you start messing with the sub-systems of Windows, it's always possible that you could make things worse if you do stuff wrong. If you're concerned about this, you should look for help from the right sources, General Tools for SAC and the Windows Group for help with WMI.

If you're bold, you could give the repository rebuild a try, one set of instructions is posted at http://www.nucleustechnologies.com/Repair-WMI-Services.php.

Mike

How To Downgrade SQL Server 2000 Enterprise Edition to Standard Ed

Two years ago, when I upgraded all my SQL Servers in our various branch
offices, I apparently took the wrong CD with me and installed Enterprise
edition when I meant to install Stanard.
Is there a procedure to downgrade an existing production SQL Server from
Enterprise Edition to Standard Edition?
ThanksI believe that there is no option but to uninstall EE and install SE.
Steps 2-9 from below:
The guide has been written to provide step by step instructions for
downgrading SQL 2000 Enterprise Edition to SQL Server Standard Edition 2000
(SP4) on the same physical server retaining all the existing databases and
settings. In this instance for VMware Virtual Center V1.3.
2. Run a database backup within sql.
3. Stop sql server service and backup all databases and log files from the
SQL data directory.
4. Uninstall SQL Enterprise Edition then Reboot the Server.
5. Install SQL 2000 STD Edition with the same database path settings.
6. Install SQL SP4 then Reboot the Server.
7. Stop SQL Server Service.
8. Copy all the backed up database and log files to the data directory
overwriting all existing files e.g. Master, temp etc.
9. Restart the SQL Server Service.
(taken from:
http://www.vmware.com/community/thread.jspa;jsessionid=FCCAFA9C91C82035C36171E6FF1484B1?messageID=386391񞕗)
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"JonMoss" <JonMoss@.discussions.microsoft.com> wrote in message
news:8936D99A-5ECF-4A5F-9D85-B37844E4274C@.microsoft.com...
> Two years ago, when I upgraded all my SQL Servers in our various branch
> offices, I apparently took the wrong CD with me and installed Enterprise
> edition when I meant to install Stanard.
> Is there a procedure to downgrade an existing production SQL Server from
> Enterprise Edition to Standard Edition?
> Thanks

How To Downgrade SQL Server 2000 Enterprise Edition to Standard Ed

Two years ago, when I upgraded all my SQL Servers in our various branch
offices, I apparently took the wrong CD with me and installed Enterprise
edition when I meant to install Stanard.
Is there a procedure to downgrade an existing production SQL Server from
Enterprise Edition to Standard Edition?
ThanksI believe that there is no option but to uninstall EE and install SE.
Steps 2-9 from below:
The guide has been written to provide step by step instructions for
downgrading SQL 2000 Enterprise Edition to SQL Server Standard Edition 2000
(SP4) on the same physical server retaining all the existing databases and
settings. In this instance for VMware Virtual Center V1.3.
2. Run a database backup within sql.
3. Stop sql server service and backup all databases and log files from the
SQL data directory.
4. Uninstall SQL Enterprise Edition then Reboot the Server.
5. Install SQL 2000 STD Edition with the same database path settings.
6. Install SQL SP4 then Reboot the Server.
7. Stop SQL Server Service.
8. Copy all the backed up database and log files to the data directory
overwriting all existing files e.g. Master, temp etc.
9. Restart the SQL Server Service.
(taken from:
http://www.vmware.com/community/thr...=386391񞕗)
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"JonMoss" <JonMoss@.discussions.microsoft.com> wrote in message
news:8936D99A-5ECF-4A5F-9D85-B37844E4274C@.microsoft.com...
> Two years ago, when I upgraded all my SQL Servers in our various branch
> offices, I apparently took the wrong CD with me and installed Enterprise
> edition when I meant to install Stanard.
> Is there a procedure to downgrade an existing production SQL Server from
> Enterprise Edition to Standard Edition?
> Thanks

How to do sizing on Memory requirement of SQL Server 2000 ?

Hi All,
We have custom application running on SQL Server 2000, about 100
users, on WIn Server 2003. The RAM installed is 1GB, very often that
the server the client getting kicked when trying to connect to the
server from custom app. Then we add to 2GB, now its getting better.
SO, I need a formula about how to determine the memory requirement of
our SQL Server 2000 on Windows Server 2003 ?
Thank you for your info,
xtantokrislioe@.gmail.com wrote:
> Hi All,
> We have custom application running on SQL Server 2000, about 100
> users, on WIn Server 2003. The RAM installed is 1GB, very often that
> the server the client getting kicked when trying to connect to the
> server from custom app. Then we add to 2GB, now its getting better.
> SO, I need a formula about how to determine the memory requirement of
> our SQL Server 2000 on Windows Server 2003 ?
> Thank you for your info,
> xtanto
You get an error when trying to connect for the first time?
I would start by addressing your connection timeout in the application
and if you are using 1GB-2GB of RAM look at the design of your database
and make sure you have good indexes. If you need to do table scans and
load everything into memory every time you do a select you will be in
trouble RAM and CPU wise.|||Marc S wrote:
> krislioe@.gmail.com wrote:
>
> You get an error when trying to connect for the first time?
> I would start by addressing your connection timeout in the application
> and if you are using 1GB-2GB of RAM look at the design of your database
> and make sure you have good indexes. If you need to do table scans and
> load everything into memory every time you do a select you will be in
> trouble RAM and CPU wise.
Looking at the design will help. But you should run performance
monitor. One thing you could do is look at Buffer Cache and Cache hit
ratios. If they are not adequate, then you could have poor written
queries and missing or improper indexes. Possible unnecessary
voluminous pages could be filling up the Buffer Cache causing it to
flush necessary pages. Then run profiler to identify processes and sql
statements unless you have a good idea what this could already be. What
I'm getting at here is there is no formula. Environments differ. That's
why real-world multi-user database applications typically need real
DBAs. Also, what I've stated above is not all you can look at. I would
do a google search on SQL Memory and start reading. Sorry there is no
easy formula.
Good Luck!!!|||Under SQL 2000 the most SQL will be able to see is 2 Gigs when running on
Win 2003 Standard. On Windows 2003 Enterprise Edition it can see more (3
Gigs with the /3 Gig switch, and the data cache can access more memory with
AWE enabled).
SQL will utilize all available memory for its caches.
There is no formula to predict how much memory your load will require as
there are many variables.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<krislioe@.gmail.com> wrote in message
news:1157559010.101762.108420@.e3g2000cwe.googlegroups.com...
> Hi All,
> We have custom application running on SQL Server 2000, about 100
> users, on WIn Server 2003. The RAM installed is 1GB, very often that
> the server the client getting kicked when trying to connect to the
> server from custom app. Then we add to 2GB, now its getting better.
> SO, I need a formula about how to determine the memory requirement of
> our SQL Server 2000 on Windows Server 2003 ?
> Thank you for your info,
> xtanto
>|||Hi Hillary,
is there any official URLS / docs about this limitation ?
Thank you,
xtanto
Hilary Cotter menuliskan:[vbcol=seagreen]
> Under SQL 2000 the most SQL will be able to see is 2 Gigs when running on
> Win 2003 Standard. On Windows 2003 Enterprise Edition it can see more (3
> Gigs with the /3 Gig switch, and the data cache can access more memory wit
h
> AWE enabled).
> SQL will utilize all available memory for its caches.
> There is no formula to predict how much memory your load will require as
> there are many variables.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> <krislioe@.gmail.com> wrote in message
> news:1157559010.101762.108420@.e3g2000cwe.googlegroups.com...

How to do sizing on Memory requirement of SQL Server 2000 ?

Hi All,
We have custom application running on SQL Server 2000, about 100
users, on WIn Server 2003. The RAM installed is 1GB, very often that
the server the client getting kicked when trying to connect to the
server from custom app. Then we add to 2GB, now its getting better.
SO, I need a formula about how to determine the memory requirement of
our SQL Server 2000 on Windows Server 2003 ?
Thank you for your info,
xtantokrislioe@.gmail.com wrote:
> Hi All,
> We have custom application running on SQL Server 2000, about 100
> users, on WIn Server 2003. The RAM installed is 1GB, very often that
> the server the client getting kicked when trying to connect to the
> server from custom app. Then we add to 2GB, now its getting better.
> SO, I need a formula about how to determine the memory requirement of
> our SQL Server 2000 on Windows Server 2003 ?
> Thank you for your info,
> xtanto
You get an error when trying to connect for the first time?
I would start by addressing your connection timeout in the application
and if you are using 1GB-2GB of RAM look at the design of your database
and make sure you have good indexes. If you need to do table scans and
load everything into memory every time you do a select you will be in
trouble RAM and CPU wise.|||Marc S wrote:
> krislioe@.gmail.com wrote:
> > Hi All,
> >
> > We have custom application running on SQL Server 2000, about 100
> > users, on WIn Server 2003. The RAM installed is 1GB, very often that
> > the server the client getting kicked when trying to connect to the
> > server from custom app. Then we add to 2GB, now its getting better.
> >
> > SO, I need a formula about how to determine the memory requirement of
> > our SQL Server 2000 on Windows Server 2003 ?
> >
> > Thank you for your info,
> > xtanto
>
> You get an error when trying to connect for the first time?
> I would start by addressing your connection timeout in the application
> and if you are using 1GB-2GB of RAM look at the design of your database
> and make sure you have good indexes. If you need to do table scans and
> load everything into memory every time you do a select you will be in
> trouble RAM and CPU wise.
Looking at the design will help. But you should run performance
monitor. One thing you could do is look at Buffer Cache and Cache hit
ratios. If they are not adequate, then you could have poor written
queries and missing or improper indexes. Possible unnecessary
voluminous pages could be filling up the Buffer Cache causing it to
flush necessary pages. Then run profiler to identify processes and sql
statements unless you have a good idea what this could already be. What
I'm getting at here is there is no formula. Environments differ. That's
why real-world multi-user database applications typically need real
DBAs. Also, what I've stated above is not all you can look at. I would
do a google search on SQL Memory and start reading. Sorry there is no
easy formula.
Good Luck!!!|||Under SQL 2000 the most SQL will be able to see is 2 Gigs when running on
Win 2003 Standard. On Windows 2003 Enterprise Edition it can see more (3
Gigs with the /3 Gig switch, and the data cache can access more memory with
AWE enabled).
SQL will utilize all available memory for its caches.
There is no formula to predict how much memory your load will require as
there are many variables.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<krislioe@.gmail.com> wrote in message
news:1157559010.101762.108420@.e3g2000cwe.googlegroups.com...
> Hi All,
> We have custom application running on SQL Server 2000, about 100
> users, on WIn Server 2003. The RAM installed is 1GB, very often that
> the server the client getting kicked when trying to connect to the
> server from custom app. Then we add to 2GB, now its getting better.
> SO, I need a formula about how to determine the memory requirement of
> our SQL Server 2000 on Windows Server 2003 ?
> Thank you for your info,
> xtanto
>|||Hi Hillary,
is there any official URLS / docs about this limitation ?
Thank you,
xtanto
Hilary Cotter menuliskan:
> Under SQL 2000 the most SQL will be able to see is 2 Gigs when running on
> Win 2003 Standard. On Windows 2003 Enterprise Edition it can see more (3
> Gigs with the /3 Gig switch, and the data cache can access more memory with
> AWE enabled).
> SQL will utilize all available memory for its caches.
> There is no formula to predict how much memory your load will require as
> there are many variables.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> <krislioe@.gmail.com> wrote in message
> news:1157559010.101762.108420@.e3g2000cwe.googlegroups.com...
> > Hi All,
> >
> > We have custom application running on SQL Server 2000, about 100
> > users, on WIn Server 2003. The RAM installed is 1GB, very often that
> > the server the client getting kicked when trying to connect to the
> > server from custom app. Then we add to 2GB, now its getting better.
> >
> > SO, I need a formula about how to determine the memory requirement of
> > our SQL Server 2000 on Windows Server 2003 ?
> >
> > Thank you for your info,
> > xtanto
> >