Registry Key for SQL Server 2005 Surface Area Configuration...

Whitch registry key should be set to allow Local and remote connections in SQL Server 2005 Surface Area configuration?May I know why you need this explicit value to update, as it is not good in terms of updating registry key on fly.

Registry entries for application to connect to remote SQL Server DB

I am trying to switch a PowerBuilder application from using a local database (SQL Anywhere) to a remote SQL Server database. I am getting IM002 after defining the data source and pointing the application to the datasource.
Can someone please send me some examples of Registry entries where an application is pointed to a remote SQL Server database?
IM002 is not a SQL Server error message. This seems to be a power builder issue, and I think you have a batter
chance to get good advice in a PowerBuilder newsgroup...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Rajeev" <rlpd@.hotmail.com> wrote in message news:72091455-61D9-475E-B9AB-5DAF5A1DE604@.microsoft.com...
> I am trying to switch a PowerBuilder application from using a local database (SQL Anywhere) to a remote SQL
Server database. I am getting IM002 after defining the data source and pointing the application to the
datasource.
> Can someone please send me some examples of Registry entries where an application is pointed to a remote SQL
Server database?

Registry entries for application to connect to remote SQL Server DB

I am trying to switch a PowerBuilder application from using a local database
(SQL Anywhere) to a remote SQL Server database. I am getting IM002 after d
efining the data source and pointing the application to the datasource.
Can someone please send me some examples of Registry entries where an applic
ation is pointed to a remote SQL Server database?IM002 is not a SQL Server error message. This seems to be a power builder is
sue, and I think you have a batter
chance to get good advice in a PowerBuilder newsgroup...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Rajeev" <rlpd@.hotmail.com> wrote in message news:72091455-61D9-475E-B9AB-5DAF5A1DE604@.micro
soft.com...
> I am trying to switch a PowerBuilder application from using a local database (SQL
Anywhere) to a remote SQL
Server database. I am getting IM002 after defining the data source and poin
ting the application to the
datasource.
> Can someone please send me some examples of Registry entries where an application
is pointed to a remote SQL
Server database?

Registry entries for application to connect to remote SQL Server DB

I am trying to switch a PowerBuilder application from using a local database (SQL Anywhere) to a remote SQL Server database. I am getting IM002 after defining the data source and pointing the application to the datasource
Can someone please send me some examples of Registry entries where an application is pointed to a remote SQL Server database?IM002 is not a SQL Server error message. This seems to be a power builder issue, and I think you have a batter
chance to get good advice in a PowerBuilder newsgroup...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Rajeev" <rlpd@.hotmail.com> wrote in message news:72091455-61D9-475E-B9AB-5DAF5A1DE604@.microsoft.com...
> I am trying to switch a PowerBuilder application from using a local database (SQL Anywhere) to a remote SQL
Server database. I am getting IM002 after defining the data source and pointing the application to the
datasource.
> Can someone please send me some examples of Registry entries where an application is pointed to a remote SQL
Server database?

Registering SQL Server in Enterprise Manager

I have followed all sugestions for this problem to no avail. I have 2 w2000 boxes connected via local network. Both are running instances of MSSQL8. From Box 2 I can register the MSSQL7 version on box1 and from box1 I can register the MSSQL7 version on box2. However I cannot register the MSSQL8 instancance either way. I can see the instance but get the message
"Specified SQL Server not found ConnectionOpen(Connect())
I have tried registering with the ip address but same problem
I have tried aliases.
In Client Network Utility and Server Network Utility I have both Named pipes(\\.\pipe\sql\query) and tcp/ip (port 1433)
on both machines
Any ideas ??
Regards ClemAre both boxes running both SQL2000 and SQL7? If so, and they are both listening on 1433, then only SQL7 will be accessible since it is not aware of multiple instancing in SQL2000. You may wish to have SQL2k listen on a different port.|||Thanks loach, sounds a likley fix. Excuse my ignorance but what port number can I use? Are port numbers listed somewhere?
Thanks for you time,
Regards Clem|||You can use any port number that is not already in use. It's typically a good idea to use port numbers over 10000 since they are rarely reserved. You can change the port number by starting up the server network utility (in the SQL Server program group), selecting the TCP/IP netowrk library and clicking on properties. To determine which ports are in use on the server, drop to a command prompt and run 'netstat -a'

You must then configure any client that accesses the server to also use that port using either the Client Network Utility or the ODBC connection properties.|||OK did that. Sql log now shows listening on [ip adds]:10000 but still same problem. tried connecting with ip adds but no go and also now on box1 I can't access the local mssql8 (7 is still ok) so i changed back to port 1433. (Is it using this port because it is not 'local'?)
At this stage I think I give up... I have been looking at this problem for about 3 months... so I guess i dont need the 7 databases any more. Any ideas how to remove the original 7 instance?
I am thinking a clean install might be the go?
Regards Clem|||Mmmmmmm clean install *drool* that's definately the way I would go,.. atleast you know where you stand then.|||try using port 1434.

try changing it in MS SQL2k on both machines (both changed at the same time)

is there any form of firewall on the individual computers, or between them? if so, make sure it isn't blocking port 1434 (or whatever port your using)

Try turning off mssql 7.

I don't know the details, but mssql is a registered system process, it integrates to an extent (i believe) with the OS.

Is it possible to successfully run multiple versions on MS SQL server on 1 machine? perhaps it isn't and that is why only ms sql 7 works correctly?

Using ports:

Yes, you can use any port, not in use. If you select a port that is in use, you should find out on the next boot. (something will probably crash, or stop working properly)

Hope this helps,|||Hi Ashleigh,
Yes it is possible to run both instances of mssql on the one server, it is the connecting to the mssql8 version on another machine that is the problem. When doing the connection the target server is even visible as a valid server...
Connecting to mssql7 on either machine is OK and of course both versions are OK if accessed on the local machine.
I believe this problem has been compounded by microsofts slammer virus fixes...

registering SQL Server behind firewall

We just implemented a SQL Server, that is in a PDMZ
(public facing dmz). It is using a local account to run
the services as it it not on our corporate network. We
cannot register the server. Does anyone know what ports
need to be open, in order to register this SQL Server? In
talking with our network folks, I'm pretty sure 1433 /
1434 are open. Any ideas...Thanks.
Tom.INF: TCP Ports Needed for Communication to SQL Server Through a Firewall
http://support.microsoft.com/?id=287932
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Tom Mongold" <tom.mongold@.stdreg.com> wrote in message
news:024a01c35606$4072e550$a401280a@.phx.gbl...
We just implemented a SQL Server, that is in a PDMZ
(public facing dmz). It is using a local account to run
the services as it it not on our corporate network. We
cannot register the server. Does anyone know what ports
need to be open, in order to register this SQL Server? In
talking with our network folks, I'm pretty sure 1433 /
1434 are open. Any ideas...Thanks.
Tom.

Registering SQL SERVER

Hi,
How to register a Remote SQL SERVER from a node in Local Area Network?You need to set up a linked server. See Linked Server in Books Online. If you need more help, let us know.

registering servers

Hi
I have to set up replication but the server is registered in EM as 'local'
so I need to delete this registration and then re-register with the correct
name. My question is in the time between deleting the old registration, and
then registering the new one, will the dbs still be available to any clients
wishing to connect?
Thanksjonjo,
This won't affect any clients - just your local machine. It takes
seconds to do and is quite safe.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
jonjo wrote:
> Hi
> I have to set up replication but the server is registered in EM as 'local'
> so I need to delete this registration and then re-register with the correc
t
> name. My question is in the time between deleting the old registration, an
d
> then registering the new one, will the dbs still be available to any clien
ts
> wishing to connect?
> Thanks|||SQLEM is and administrative client API, but it is still just a client. That
is, it is localized the user and/or workstation that hosts the installation,
not the DBMS.
Sincerely,
Anthony Thomas
"jonjo" <jonjo@.discussions.microsoft.com> wrote in message
news:B04A35E0-D628-49AA-A6D8-E70BF976D8F3@.microsoft.com...
Hi
I have to set up replication but the server is registered in EM as 'local'
so I need to delete this registration and then re-register with the correct
name. My question is in the time between deleting the old registration, and
then registering the new one, will the dbs still be available to any clients
wishing to connect?
Thanks

registering servers

Hi
I have to set up replication but the server is registered in EM as 'local'
so I need to delete this registration and then re-register with the correct
name. My question is in the time between deleting the old registration, and
then registering the new one, will the dbs still be available to any clients
wishing to connect?
Thanksjonjo,
This won't affect any clients - just your local machine. It takes
seconds to do and is quite safe.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
jonjo wrote:
> Hi
> I have to set up replication but the server is registered in EM as 'local'
> so I need to delete this registration and then re-register with the correct
> name. My question is in the time between deleting the old registration, and
> then registering the new one, will the dbs still be available to any clients
> wishing to connect?
> Thanks|||SQLEM is and administrative client API, but it is still just a client. That
is, it is localized the user and/or workstation that hosts the installation,
not the DBMS.
Sincerely,
Anthony Thomas
"jonjo" <jonjo@.discussions.microsoft.com> wrote in message
news:B04A35E0-D628-49AA-A6D8-E70BF976D8F3@.microsoft.com...
Hi
I have to set up replication but the server is registered in EM as 'local'
so I need to delete this registration and then re-register with the correct
name. My question is in the time between deleting the old registration, and
then registering the new one, will the dbs still be available to any clients
wishing to connect?
Thanks

registering new sql server

Hello,
I have SQL server developer version running on my local workstation.
I recently got a new Win 2003 Box.
Couple of things.
1) IT dept gave me 35 gigs are raid 5. Is this enough for a large DB?
It seems awfully small to me.
2) The SQL server is running all well. In my local Enterprise Manger.
I tried to register a sql server. But I can't get a connect() back.
What could be causing this? I can ping the SQL box because it's on the
same subnet.
Won Lee> 1) IT dept gave me 35 gigs are raid 5. Is this enough for a large DB?
> It seems awfully small to me.
Depends on what you consider a large db. We've got a sql database just over
1 million records spread across 100 tables with that many views and stored
procedures besides, and that's 2gb.
> 2) The SQL server is running all well. In my local Enterprise Manger.
> I tried to register a sql server. But I can't get a connect() back.
> What could be causing this? I can ping the SQL box because it's on the
> same subnet.
Did you set up an alias in the Client Network Utility?|||> 1) IT dept gave me 35 gigs are raid 5. Is this enough for a large DB?
> It seems awfully small to me.
Only you can tell us how large your database is going to be. You need to
research your business requirements and determine size and growth from that.
There's no such thing as a "typical" size for a database.
> I tried to register a sql server. But I can't get a connect() back.
Can you give some more detail. Do you get an error message? Can you verify
in Service Manager that the server is running? Did you supply a valid user
name and password?
This might also help:
http://support.microsoft.com/?id=328306
David Portas
--
Please reply only to the newsgroup
--|||William Morris wrote:
>>1) IT dept gave me 35 gigs are raid 5. Is this enough for a large DB?
>>It seems awfully small to me.
>
> Depends on what you consider a large db. We've got a sql database just over
> 1 million records spread across 100 tables with that many views and stored
> procedures besides, and that's 2gb.
>
Thanks. I looked at the old DB and realized that we only grew at a 3
meg per month rate. I guess the DB is good for awhile.
>>2) The SQL server is running all well. In my local Enterprise Manger.
>>I tried to register a sql server. But I can't get a connect() back.
>>What could be causing this? I can ping the SQL box because it's on the
>>same subnet.
>
> Did you set up an alias in the Client Network Utility?
I didn't do anything. My IT guys set up the box. The error message I'm
getting is, WINBOX-SQL server does not exist or access denied.
I created a user as a DBO owner. I also tried with the SA login
credentials. I can remote desktop into the server and login to the SQL
server through Enterprise Manager and Query Analyzer.
I have no idea what Client Network Utility is so I looked it up in Books
Online. I will give that a try.
BTW How do I find out if they installed the Developer version or the
client/server version of SQL Server 2000?|||> Can you give some more detail. Do you get an error message? Can you verify
> in Service Manager that the server is running? Did you supply a valid user
> name and password?
> This might also help:
> http://support.microsoft.com/?id=328306
>
David,
Yes the service is started. I did created a user and also used the SA
password to login locally.
Thanks for the KB article I will look through it.|||> This might also help:
> http://support.microsoft.com/?id=328306
>
Just in case anyone is insterested.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;306199
A link from the KB article David posted fixed the problem. Funny thing
is that the server is not on DHCP. It was when we first popped it in to
the rack but promptly changed it to a fixed IP address. Kinda funny.
But at least it works now.|||Thanks to William and David for helping me out.
Won Lee

register local instance with MSDE

Thanks in advance.
I am trying to register my local machine with MSDE 2000.
SQL server authetication keep rejecting my login id and password.
Please, advised me why it is not accepting.
Is it because I don't have installed server portion of SQL 2000 Server?
What exactly do you mean "register local instance with MSDE"?
When you say "SQL Server authentication keep rejecting my login id and
password", do you mean you was trying to connect to the MSDE by supplying
username/password pair (meaning the MSDE must be enabled on mixed security
mode)? Since by default installation, only Windows Integrated Authentication
mode is enabled, unless you specifically enabled mixed security mode on the
MSDE, you will not be able to access the MSDE by supplying
username/password. This could be the cause of your problem.
"Jay" <Jay@.discussions.microsoft.com> wrote in message
news:C83EC5C8-012D-4155-AA55-5228713A967C@.microsoft.com...
> Thanks in advance.
> I am trying to register my local machine with MSDE 2000.
> SQL server authetication keep rejecting my login id and password.
> Please, advised me why it is not accepting.
> Is it because I don't have installed server portion of SQL 2000 Server?
>
>
|||Thank you Norman for your clarification.
In MSDE SQL Server Enterprise Manage, under Microsoft Servers and SQL Server
Groups, I am trying to connect (LOCAL)(Windows NT: this is my local machine).
I am having this error message: Connection Failed, check SQL server
Registration
1.Using Windows Authentication in "Edit SQL Server Registration Properties"
Error message: A connection can not be established to (LOCAL).
Reason: Login failed
2.SQL Server Authentication in "Edit SQL Server Registration Properties"
Error message: SQL server registration failed.
Login failed for user.
3. Network administrator can connect to this "LOCAL" machine.
Will you help me to clear oou my confused minds?
Thanks, again.
"Norman Yuan" wrote:

> What exactly do you mean "register local instance with MSDE"?
> When you say "SQL Server authentication keep rejecting my login id and
> password", do you mean you was trying to connect to the MSDE by supplying
> username/password pair (meaning the MSDE must be enabled on mixed security
> mode)? Since by default installation, only Windows Integrated Authentication
> mode is enabled, unless you specifically enabled mixed security mode on the
> MSDE, you will not be able to access the MSDE by supplying
> username/password. This could be the cause of your problem.
> "Jay" <Jay@.discussions.microsoft.com> wrote in message
> news:C83EC5C8-012D-4155-AA55-5228713A967C@.microsoft.com...
>
>
|||There is no such product as: "MSDE SQL Server Enterprise Manage".
Are you using EM with a properly licensed SQL Server installation?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Jay" <Jay@.discussions.microsoft.com> wrote in message
news:8CBFEED6-75E2-4215-9D38-B55F8E98F348@.microsoft.com...[vbcol=seagreen]
> Thank you Norman for your clarification.
> In MSDE SQL Server Enterprise Manage, under Microsoft Servers and SQL
> Server
> Groups, I am trying to connect (LOCAL)(Windows NT: this is my local
> machine).
> I am having this error message: Connection Failed, check SQL server
> Registration
> 1.Using Windows Authentication in "Edit SQL Server Registration
> Properties"
> Error message: A connection can not be established to (LOCAL).
> Reason: Login failed
> 2.SQL Server Authentication in "Edit SQL Server Registration Properties"
> Error message: SQL server registration failed.
> Login failed for user.
> 3. Network administrator can connect to this "LOCAL" machine.
> Will you help me to clear oou my confused minds?
> Thanks, again.
>
> "Norman Yuan" wrote:
|||Sorry for confusion!
I just put MSDE in front of SQL Server Enterprise Manager to emphasize that
it is MSDE not SQL Server.
Thanks
"Arnie Rowland" wrote:

> There is no such product as: "MSDE SQL Server Enterprise Manage".
> Are you using EM with a properly licensed SQL Server installation?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to the
> top yourself.
> - H. Norman Schwarzkopf
>
> "Jay" <Jay@.discussions.microsoft.com> wrote in message
> news:8CBFEED6-75E2-4215-9D38-B55F8E98F348@.microsoft.com...
>
>