Cluster under sqlserver 2000

I would like to know if the clustering under sqlserver 2000 works fine.
Could you give some pointers in order to install a cluster under sqlserver ?
Best regardsorion30,
Yes SQL Server has fault tolerance capabilities which can be implemented with
the help of its clustering feature. SQL Server has two types of cluster
configuration ie Active/Active and Active/Passive cluster.
A cluster is a safeguard for fault tolerance for the servers, the operating
system, and the software. You can safeguard the data with the help of shared
disk arrays.
MS has a clustering feature to its operating system in Windows NT 4.0 Enterprise
Edition / WIN2K advanced & datacenter servers, this clustering feature is called
MSCS ie Microsoft Clustering Server. SQL Server's enterprise edition ships with
Clustering feature(Virtual Server).
For more information on cluster visit this url
http://www.sql-server-performance.com/clustering_intro1.asp
Also you can post your queries to more relevent newgroup
microsoft.public.sqlserver.clustering
-- Vishal
"orion30" <orion30@.ifrance.com> wrote in message
news:bri7f1$bvi$1@.news-reader5.wanadoo.fr...
> I would like to know if the clustering under sqlserver 2000 works fine.
> Could you give some pointers in order to install a cluster under sqlserver ?
> Best regards
>

Cluster SQL 7.0 in W2KAdv environment

Hi!
This is the scenario:
* Windows 2000 Advanced Server clustered with 2 nodes
After the installation of SQLServer in the first node, does not appear
the 'SQL Server Failover Cluster' or 'Failover Cluster Wizard' in the
program files menu, and the option 'MSDTC Administrative Control' is
in the menu but the file 'dac.exe' isn't installed.
I don't know which is the problem, because the MSDTC resource in the
cluster is on-line and managed by the firt node, after execute the
command comclust. I see the articles in Microsoft KB (290624, 243204,
), but I don't found a solutions. There are a special SQL 7.0 version
for clustering
Thanks!!
Are you sure you installed the Enterprise Edition?
Look at the SQL Server errorlog and verify that you installed the
Enterprise Edition. BAsed on what you are saying about the Failover Wizard
not being there I am thinking that you did not.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I fix this problem by installing the Enterprise Edition (really stupid
), and now the Failover Wizard it's ok, but the 'MSDTC
Administrative Console' still not work. I don't know the reason why
don't install dac.exe. I'll try to install mdac2.8
Thanks for your post.
Regards,
Ren
rboyd@.onlinemicrosoft.com (Rand Boyd [MSFT]) wrote in message news:<CxzmcDlJEHA.4016@.cpmsftngxa10.phx.gbl>...
> Are you sure you installed the Enterprise Edition?
> Look at the SQL Server errorlog and verify that you installed the
> Enterprise Edition. BAsed on what you are saying about the Failover Wizard
> not being there I am thinking that you did not.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.

cluster check

Guys,
Apart from cluster administrator, is there any way to check from inside SQL
server to know whether a particular installation is clustered?
select serverproperty('IsClustered') will tell you if a particular instance
is part of a cluster
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:A33FB883-4923-45A0-BAA8-434B5530D971@.microsoft.com...
> Guys,
> Apart from cluster administrator, is there any way to check from inside
> SQL
> server to know whether a particular installation is clustered?
|||thanks jasper...
"Jasper Smith" wrote:

> select serverproperty('IsClustered') will tell you if a particular instance
> is part of a cluster
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Bharath" <Bharath@.discussions.microsoft.com> wrote in message
> news:A33FB883-4923-45A0-BAA8-434B5530D971@.microsoft.com...
>
>

cluster check

Guys,
Apart from cluster administrator, is there any way to check from inside SQL
server to know whether a particular installation is clustered?select serverproperty('IsClustered') will tell you if a particular instance
is part of a cluster
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:A33FB883-4923-45A0-BAA8-434B5530D971@.microsoft.com...
> Guys,
> Apart from cluster administrator, is there any way to check from inside
> SQL
> server to know whether a particular installation is clustered?|||thanks jasper...
"Jasper Smith" wrote:

> select serverproperty('IsClustered') will tell you if a particular instanc
e
> is part of a cluster
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Bharath" <Bharath@.discussions.microsoft.com> wrote in message
> news:A33FB883-4923-45A0-BAA8-434B5530D971@.microsoft.com...
>
>

CLR Question (BASIC)

I have Visual Studio .Net 2003...I am assuming that since it can't find
System.Data.SQLServer that I need Visual Studio 2005 to develop CLR apps for
SQL?Hello RSH,

> I have Visual Studio .Net 2003...I am assuming that since it can't
> find System.Data.SQLServer that I need Visual Studio 2005 to develop
> CLR apps for SQL?
Correct
Thank you,
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/|||There's no System.Data.SQLServer anymore. You use the regular connection obj
ects, reader etc. For
SQLCLR specific things (like context and pipe), you use the Microsoft.SqlSer
ver.Server namespace.
You do need Framework 2.0 (as the things you need are in the System.Data.dll
file that comes with
Framework 2.0). You can download Framework 2.0 and write your CLR objects us
ing Notepad and
command-line compile them. If you want to use VS to write SQLCLR objects you
need VS 2005.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"RSH" <way_beyond_oops@.yahoo.com> wrote in message news:ejDCfJ29FHA.160@.TK2MSFTNGP12.phx.gb
l...
>I have Visual Studio .Net 2003...I am assuming that since it can't find Sys
tem.Data.SQLServer that
>I need Visual Studio 2005 to develop CLR apps for SQL?
>|||You don't really need Visual Studio at all. You can download the .NET 2.0
SDK and use the command-line tools. But if you want the IDE experience,
yes, VS2005 is necessary.
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
--
"RSH" <way_beyond_oops@.yahoo.com> wrote in message
news:ejDCfJ29FHA.160@.TK2MSFTNGP12.phx.gbl...
>I have Visual Studio .Net 2003...I am assuming that since it can't find
>System.Data.SQLServer that I need Visual Studio 2005 to develop CLR apps
>for SQL?
>

CLR out of memory

I've got a CLR function that runs fine on my workstation running SQL
Server Express; however, it throws OOM exceptions on the full SQL
Server 2005.
The function is very simple: it takes an XML file and a stylesheet,
transforms the XML using the stylesheet, and returns the result as a
string. On my workstation, with 2 gb RAM (1gb allocated to SQL Server),
I hardly ever have any problem with it. On the server, with 4gb, the
same function running on the same data terminates with the following
message:
.NET Framework execution was aborted by escalation policy because of
out of memory.
System.Threading.ThreadAbortException: Thread was being aborted.
(...stack follows...)
This happens when input XML data size exceeds ~30-50 mb or so.
I checked performance counters and memory clerks. The problem seems to
be that CLR never grabs enough memory even when it should be available.
I ran the same request on the same data, first on my workstation, then
on the server. On the workstation, once the function was started, CLR
memory utilization went up to about 108 megs, and the function
completed normally. On the server, the CLR memory utilization only went
up to about 75 megs, then the function was terminated.
I checked command line parameters - the -g switch was not used at
either the server or the workstation. Just in case, I added the default
-g256 at the server, to no effect.
So, my question is - what could cause the CLR to not use available
memory? There's something wrong with the server configuration, but I
can't figure out what. Any help would be greatly appreciated!
Below is the function in question.
[SqlFunction(Name="_clrApplyStylesheet",
DataAccess=DataAccessKind.Read)]
public static SqlString _clrApplyStylesheet(SqlXml XmlData,
SqlXml XmlStylesheet)
{
XPathDocument stylesheet, xmlData;
XslCompiledTransform xTransform;
System.Text.StringBuilder sBuilder;
XmlWriter xWriter;
stylesheet = new
XPathDocument(XmlStylesheet.CreateReader());
xmlData = new XPathDocument(XmlData.CreateReader());
sBuilder = new System.Text.StringBuilder();
xWriter = XmlWriter.Create(sBuilder);
xTransform = new XslCompiledTransform();
xTransform.Load(stylesheet);
xTransform.Transform(xmlData, xWriter);
return sBuilder.ToString();
}Hi Abe,
I mentioned this problem briefly here:
http://blogs.msdn.com/sqlclr/archiv.../24/560154.aspx
The issue you are seeing is not because of a lack in physical memory but in
a lack of Virtual Address Space. If you have 1 GB allocated to SQL on your
workstation, then the SQL Buffer Pool will reserve 1 GB of VAS for its use,
leaving 1 GB for all the allocations made outside the buffer pool, including
CLR. However, as you found and contrary to what you expected, on your
server the Buffer Pool is able to use much more memory (depending on if you
are using AWE or /3GB) leaving only the default 256 MB of VAS for everything
else.
Unfortunately, I think your only real options would be to use the -g flag to
reserve more memory for allocations outside the buffer pool or, if possible,
use 64-bit hardware.
Steven
"Abe" <revres_lqs@.yahoo.com> wrote in message
news:1152829807.975377.50710@.35g2000cwc.googlegroups.com...
> I've got a CLR function that runs fine on my workstation running SQL
> Server Express; however, it throws OOM exceptions on the full SQL
> Server 2005.
> The function is very simple: it takes an XML file and a stylesheet,
> transforms the XML using the stylesheet, and returns the result as a
> string. On my workstation, with 2 gb RAM (1gb allocated to SQL Server),
> I hardly ever have any problem with it. On the server, with 4gb, the
> same function running on the same data terminates with the following
> message:
> .NET Framework execution was aborted by escalation policy because of
> out of memory.
> System.Threading.ThreadAbortException: Thread was being aborted.
> (...stack follows...)
> This happens when input XML data size exceeds ~30-50 mb or so.
> I checked performance counters and memory clerks. The problem seems to
> be that CLR never grabs enough memory even when it should be available.
> I ran the same request on the same data, first on my workstation, then
> on the server. On the workstation, once the function was started, CLR
> memory utilization went up to about 108 megs, and the function
> completed normally. On the server, the CLR memory utilization only went
> up to about 75 megs, then the function was terminated.
> I checked command line parameters - the -g switch was not used at
> either the server or the workstation. Just in case, I added the default
> -g256 at the server, to no effect.
> So, my question is - what could cause the CLR to not use available
> memory? There's something wrong with the server configuration, but I
> can't figure out what. Any help would be greatly appreciated!
> Below is the function in question.
> [SqlFunction(Name="_clrApplyStylesheet",
> DataAccess=DataAccessKind.Read)]
> public static SqlString _clrApplyStylesheet(SqlXml XmlData,
> SqlXml XmlStylesheet)
> {
> XPathDocument stylesheet, xmlData;
> XslCompiledTransform xTransform;
> System.Text.StringBuilder sBuilder;
> XmlWriter xWriter;
> stylesheet = new
> XPathDocument(XmlStylesheet.CreateReader());
> xmlData = new XPathDocument(XmlData.CreateReader());
>
> sBuilder = new System.Text.StringBuilder();
> xWriter = XmlWriter.Create(sBuilder);
> xTransform = new XslCompiledTransform();
> xTransform.Load(stylesheet);
> xTransform.Transform(xmlData, xWriter);
> return sBuilder.ToString();
> }
>|||Hi Steven,
Thank you so much - I increased memory allocation with the -g switch,
and it worked!
I wonder why it's such an obscure issue - your article (which I read
even before posting but wasn't sure if it was applicable) seems to be
almost the only one relevant to the issue.
So, when you do use the -g switch: can the Buffer Pool reclaim the
memory from "memtoleave" when it's not required, or are you actually
decreasing the memory available to Buffer Pool at all times? It's a
shared server, and I don't want to slow down everyone just so that my
code could work.
Abe

clr integration....

sir here are the functions on my test application...

<Microsoft.SqlServer.Server.SqlFunction()> _

Public Shared Function WeekInYear(ByVal dt As DateTime) As Integer

Return DatePart("ww", dt, FirstDayOfWeek.Monday, _

FirstWeekOfYear.FirstFourDays)

End Function

<Microsoft.SqlServer.Server.SqlFunction()> _

Public Shared Function HttpPost(ByVal uri As String, ByVal parameters As String) As String

Try

Dim urlRegEx As New System.Text.RegularExpressions.Regex("http://192.168.1.23:81/.*")

Dim p As New System.Net.WebPermission(System.Net.NetworkAccess.Connect, urlRegEx)

p.Assert()

Dim req As System.Net.WebRequest = System.Net.WebRequest.Create(uri)

req.ContentType = "application/x-www-form-urlencoded;charset=utf-8"

req.Method = "POST"

Try

Dim bytes() As Byte = System.Text.Encoding.UTF8.GetBytes(parameters)

req.ContentLength = bytes.Length

Dim os As System.IO.Stream = req.GetRequestStream

os.Write(bytes, 0, bytes.Length)

'Push it out there

os.Close()

Catch ex As Exception

Throw New Exception(ex.Message)

End Try

Dim resp As System.Net.WebResponse = req.GetResponse

If resp Is Nothing Then

Return Nothing

End If

Return "pass completed"

Catch ex As Exception

Return ex.Message

Finally

End Try

End Function

the first function works fine, the second function doesn't work, it seems that if i ever use another namespace it requires a security permission.

can you specify why do i recieved this error at runtime?

Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

You have to give the assembly the appropiate permissions in SQL Server. By default only a few assemblies / namespaces are *trusted*. Try to give more access to the assembly by registering the assenblies as UNSAFE or external_Access.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

As Jens says, the most likely issue is that you haven't created the assembly with a permission set that allows you to do web "stuff". For that to work you need to create the assembly with a permission set of EXTERNAL_ACCESS.

Niels

Clone SQL SERVER question

Hello Guys,
I am working in a clone of SQL server and I have some question:
NEW SQLSERVER = Copy of OLD SQLSERVER
As the new sql server "NEW SQLSERVER" has the same configuration as
the "OLD SQLSERVER" all the jobs and others setups have still the old
"OLD SQLSERVER" settings. I have already done this operation for the
backups.
update backupset
set machine_name= 'NEW SQLSERVER'
where machine_name = 'OLD SQLSERVER'
what do you advice me to do in order to set up this machine currently
Any suggestion will be appreciate
Ina
Hi
Have you scripted the jobs and changed any references to the old server? Are
there any hard coded references in Stored procedure, triggers, views etc?
DTS packages can be exported using the DTS Backup tool
http://www.sqldts.com/default.aspx?242
Are you using replication?
If the server is not on the same domain or if you had local accounts for
logins, you will have to change them see
http://support.microsoft.com/kb/246133/. It may be necessary to also change
orphaned users http://support.microsoft.com/kb/274188/
John
"ina" wrote:

> Hello Guys,
> I am working in a clone of SQL server and I have some question:
> NEW SQLSERVER = Copy of OLD SQLSERVER
> As the new sql server "NEW SQLSERVER" has the same configuration as
> the "OLD SQLSERVER" all the jobs and others setups have still the old
> "OLD SQLSERVER" settings. I have already done this operation for the
> backups.
> update backupset
> set machine_name= 'NEW SQLSERVER'
> where machine_name = 'OLD SQLSERVER'
> what do you advice me to do in order to set up this machine currently
> Any suggestion will be appreciate
> Ina
>
|||Thanks John,
I haven't done anything concerning replication, views and triggers in
the old server, I had only setup up backups and maintenance plans.
Thanks for this documents I will get through.
Ina
Thank you a lot for all
John Bell wrote:[vbcol=seagreen]
> Hi
> Have you scripted the jobs and changed any references to the old server? Are
> there any hard coded references in Stored procedure, triggers, views etc?
> DTS packages can be exported using the DTS Backup tool
> http://www.sqldts.com/default.aspx?242
> Are you using replication?
> If the server is not on the same domain or if you had local accounts for
> logins, you will have to change them see
> http://support.microsoft.com/kb/246133/. It may be necessary to also change
> orphaned users http://support.microsoft.com/kb/274188/
>
> John
> "ina" wrote:

Clone SQL SERVER question

Hello Guys,
I am working in a clone of SQL server and I have some question:
NEW SQLSERVER = Copy of OLD SQLSERVER
As the new sql server "NEW SQLSERVER" has the same configuration as
the "OLD SQLSERVER" all the jobs and others setups have still the old
"OLD SQLSERVER" settings. I have already done this operation for the
backups.
update backupset
set machine_name= 'NEW SQLSERVER'
where machine_name = 'OLD SQLSERVER'
what do you advice me to do in order to set up this machine currently
Any suggestion will be appreciate
InaHi
Have you scripted the jobs and changed any references to the old server? Are
there any hard coded references in Stored procedure, triggers, views etc?
DTS packages can be exported using the DTS Backup tool
http://www.sqldts.com/default.aspx?242
Are you using replication?
If the server is not on the same domain or if you had local accounts for
logins, you will have to change them see
http://support.microsoft.com/kb/246133/. It may be necessary to also change
orphaned users http://support.microsoft.com/kb/274188/
John
"ina" wrote:
> Hello Guys,
> I am working in a clone of SQL server and I have some question:
> NEW SQLSERVER = Copy of OLD SQLSERVER
> As the new sql server "NEW SQLSERVER" has the same configuration as
> the "OLD SQLSERVER" all the jobs and others setups have still the old
> "OLD SQLSERVER" settings. I have already done this operation for the
> backups.
> update backupset
> set machine_name= 'NEW SQLSERVER'
> where machine_name = 'OLD SQLSERVER'
> what do you advice me to do in order to set up this machine currently
> Any suggestion will be appreciate
> Ina
>|||Thanks John,
I haven't done anything concerning replication, views and triggers in
the old server, I had only setup up backups and maintenance plans.
Thanks for this documents I will get through.
Ina
Thank you a lot for all
John Bell wrote:
> Hi
> Have you scripted the jobs and changed any references to the old server? Are
> there any hard coded references in Stored procedure, triggers, views etc?
> DTS packages can be exported using the DTS Backup tool
> http://www.sqldts.com/default.aspx?242
> Are you using replication?
> If the server is not on the same domain or if you had local accounts for
> logins, you will have to change them see
> http://support.microsoft.com/kb/246133/. It may be necessary to also change
> orphaned users http://support.microsoft.com/kb/274188/
>
> John
> "ina" wrote:
> > Hello Guys,
> >
> > I am working in a clone of SQL server and I have some question:
> >
> > NEW SQLSERVER = Copy of OLD SQLSERVER
> >
> > As the new sql server "NEW SQLSERVER" has the same configuration as
> > the "OLD SQLSERVER" all the jobs and others setups have still the old
> > "OLD SQLSERVER" settings. I have already done this operation for the
> > backups.
> >
> > update backupset
> > set machine_name= 'NEW SQLSERVER'
> > where machine_name = 'OLD SQLSERVER'
> >
> > what do you advice me to do in order to set up this machine currently
> >
> > Any suggestion will be appreciate
> >
> > Ina
> >
> >

Clone SQL SERVER question

Hello Guys,
I am working in a clone of SQL server and I have some question:
NEW SQLSERVER = Copy of OLD SQLSERVER
As the new sql server "NEW SQLSERVER" has the same configuration as
the "OLD SQLSERVER" all the jobs and others setups have still the old
"OLD SQLSERVER" settings. I have already done this operation for the
backups.
update backupset
set machine_name= 'NEW SQLSERVER'
where machine_name = 'OLD SQLSERVER'
what do you advice me to do in order to set up this machine currently
Any suggestion will be appreciate
InaHi
Have you scripted the jobs and changed any references to the old server? Are
there any hard coded references in Stored procedure, triggers, views etc?
DTS packages can be exported using the DTS Backup tool
http://www.sqldts.com/default.aspx?242
Are you using replication?
If the server is not on the same domain or if you had local accounts for
logins, you will have to change them see
http://support.microsoft.com/kb/246133/. It may be necessary to also change
orphaned users http://support.microsoft.com/kb/274188/
John
"ina" wrote:

> Hello Guys,
> I am working in a clone of SQL server and I have some question:
> NEW SQLSERVER = Copy of OLD SQLSERVER
> As the new sql server "NEW SQLSERVER" has the same configuration as
> the "OLD SQLSERVER" all the jobs and others setups have still the old
> "OLD SQLSERVER" settings. I have already done this operation for the
> backups.
> update backupset
> set machine_name= 'NEW SQLSERVER'
> where machine_name = 'OLD SQLSERVER'
> what do you advice me to do in order to set up this machine currently
> Any suggestion will be appreciate
> Ina
>|||Thanks John,
I haven't done anything concerning replication, views and triggers in
the old server, I had only setup up backups and maintenance plans.
Thanks for this documents I will get through.
Ina
Thank you a lot for all
John Bell wrote:[vbcol=seagreen]
> Hi
> Have you scripted the jobs and changed any references to the old server? A
re
> there any hard coded references in Stored procedure, triggers, views etc?
> DTS packages can be exported using the DTS Backup tool
> http://www.sqldts.com/default.aspx?242
> Are you using replication?
> If the server is not on the same domain or if you had local accounts for
> logins, you will have to change them see
> http://support.microsoft.com/kb/246133/. It may be necessary to also chang
e
> orphaned users http://support.microsoft.com/kb/274188/
>
> John
> "ina" wrote:
>

Client Tools for SQL Server

Where exactly does one find the installation package for Client Tools for SQL
Server. SQL Server 2003 running on a Win2003 server. Workstations now
need console, etc. ODBC links from the workstation to the server work fine.
Thanks.
Not sure what you mean by installation package - are you
trying to install just the client tools or are you looking
for sqlredis which installs the client components? sqlredis
is the distribution executable that installs the client
components (not client tools). There is info on this in
books online. But it sounds like you want to install the
client tools such as Enterprise Manager, Query Analyzer,
etc. You can use the SQL Server installation CD. Refer to
the topic in books online:
How to install client tools only (Setup)
-Sue
On Mon, 28 Mar 2005 14:49:03 -0800, "Gene"
<justasking@.newsql.user.com> wrote:

>Where exactly does one find the installation package for Client Tools for SQL
>Server. SQL Server 2003 running on a Win2003 server. Workstations now
>need console, etc. ODBC links from the workstation to the server work fine.
>Thanks.

Client Net Library Changes

I have been asked to consider changing the Net Library TCP/IP port for SQL
Server from the default 1433 to a different one.
The problem is the 1800 user stations.
Is there a scriptable way to change the port on the clients without having
to visit each one to do it manually?When you create an alias o the client (start->run->cliconfg.exe->alias tab)
- a registry key value with the alias properties will be created under:
HKLM\SW\Microsoft\MSSQLServer\Client\Con
nectTo . So you can write a script
to add this registry key value. If this a named instance then the clients
should be able to "dynamically" determine the port number and no registry
key modification should be necessary.
See the MSDN article : How To Use the Windows Script Host to Read, Write,
and Delete Registry Keys
for more details on how to write to the registry through script.
reference:
Books online topics:
- Client Network Utility
- Managing Clients
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Client Net Library Changes

I have been asked to consider changing the Net Library TCP/IP port for SQL
Server from the default 1433 to a different one.
The problem is the 1800 user stations.
Is there a scriptable way to change the port on the clients without having
to visit each one to do it manually?
When you create an alias o the client (start->run->cliconfg.exe->alias tab)
- a registry key value with the alias properties will be created under:
HKLM\SW\Microsoft\MSSQLServer\Client\ConnectTo . So you can write a script
to add this registry key value. If this a named instance then the clients
should be able to "dynamically" determine the port number and no registry
key modification should be necessary.
See the MSDN article : How To Use the Windows Script Host to Read, Write,
and Delete Registry Keys
for more details on how to write to the registry through script.
reference:
Books online topics:
- Client Network Utility
- Managing Clients
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Client Hang

Hello,
We han a SQL Server Developer Edition (64-Bit) versión 8.00.760(SP3) that hangs our SQLServer Clients after starting a DTC transaction.
SQL Server service starts automatically at startup and it starts DTC.
?Does anybody know how to solve the problem and what is happening?

> Hello,
> We han a SQL Server Developer Edition (64-Bit) versión 8.00.760(SP3)
> that hangs our SQLServer Clients after starting a DTC transaction.
> SQL Server service starts automatically at startup and it starts DTC.
> ?Does anybody know how to solve the problem and what is happening?
>
It could be an MS DTC problem. You can use a tool named DTCPing to
troubleshoot MS DTC operation:
HOWTO: Troubleshoot MS DTC Firewall Issues
http://support.microsoft.com/?id=306843
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Client Hang

Hello
We han a SQL Server Developer Edition (64-Bit) versión 8.00.760(SP3) that hangs our SQLServer Clients after starting a DTC transaction
SQL Server service starts automatically at startup and it starts DTC
¿Does anybody know how to solve the problem and what is happening?> Hello,
> We han a SQL Server Developer Edition (64-Bit) versión 8.00.760(SP3)
> that hangs our SQLServer Clients after starting a DTC transaction.
> SQL Server service starts automatically at startup and it starts DTC.
> ¿Does anybody know how to solve the problem and what is happening?
>
--
It could be an MS DTC problem. You can use a tool named DTCPing to
troubleshoot MS DTC operation:
HOWTO: Troubleshoot MS DTC Firewall Issues
http://support.microsoft.com/?id=306843
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Client Hang

Hello,
We han a SQL Server Developer Edition (64-Bit) versión 8.00.760(SP3) that h
angs our SQLServer Clients after starting a DTC transaction.
SQL Server service starts automatically at startup and it starts DTC.
?Does anybody know how to solve the problem and what is happening?
> Hello,
> We han a SQL Server Developer Edition (64-Bit) versión 8.00.760(SP3)
> that hangs our SQLServer Clients after starting a DTC transaction.
> SQL Server service starts automatically at startup and it starts DTC.
> ?Does anybody know how to solve the problem and what is happening?
>
--
It could be an MS DTC problem. You can use a tool named DTCPing to
troubleshoot MS DTC operation:
HOWTO: Troubleshoot MS DTC Firewall Issues
http://support.microsoft.com/?id=306843
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Client can not see DBs

When i run the SQLDATAadapter it cannot find the SQL
server 2000. the error it gives is:
Provider Cannnot be found. It may not be properly
installed. I am running out of Ideas any help will nice?
Thanks
Tom
If you are using MSDE, make sure you have a network protocol (TCP/IP)
enabled in the Server Network Utility for SQL Server.
"TOM" <tbeyerlein@.microsoft.com> wrote in message
news:123f01c4f512$6561ef30$a401280a@.phx.gbl...
> When i run the SQLDATAadapter it cannot find the SQL
> server 2000. the error it gives is:
> Provider Cannnot be found. It may not be properly
> installed. I am running out of Ideas any help will nice?
> Thanks
> Tom
|||I am not using MSDE, i only installed the client tools
form the SQL server 2000. Do i need to install MSDE?

>--Original Message--
>If you are using MSDE, make sure you have a network
protocol (TCP/IP)
>enabled in the Server Network Utility for SQL Server.
>
>"TOM" <tbeyerlein@.microsoft.com> wrote in message
>news:123f01c4f512$6561ef30$a401280a@.phx.gbl...
>
>.
>
|||Well, if you only installed the client tools, there isn't a database to
connect to. The Server component is what SQLDataAdaptor would actually
connect to.
"TOM" <tbeyerlein@.microconstants.com> wrote in message
news:125601c4f734$14af9d70$a501280a@.phx.gbl...[vbcol=seagreen]
> I am not using MSDE, i only installed the client tools
> form the SQL server 2000. Do i need to install MSDE?
>
> protocol (TCP/IP)