Can not connect to non-default instance from remote computer

I installed SQL2005 as default instance.
After that I installed SQL2000 with instance name "SQL2K". Then I installed
SP4.
I can'not connect to SQL2K instance from remote machine. But if I log on at
machine on which SQL Server installed I can connect to instance.
And I can connect to default instance (SQL2005) from remote machine.
How to solve this problem?
Is the SQL Server Browser service running? It helps resolve names of named
instances to the port number. Since SQL Server 2005 is the default instance,
it is probably using port 1433. Therefore SQL Server 2000 must be using some
other port, but you don't know which port, but the SQL Server Browser
service will know.
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Alexey Rokhin" <ar@.hotmail.com> wrote in message
news:%23PF4wc16FHA.1416@.TK2MSFTNGP09.phx.gbl...
>I installed SQL2005 as default instance.
> After that I installed SQL2000 with instance name "SQL2K". Then I
> installed SP4.
> I can'not connect to SQL2K instance from remote machine. But if I log on
> at machine on which SQL Server installed I can connect to instance.
> And I can connect to default instance (SQL2005) from remote machine.
> How to solve this problem?
>

Can not connect to non-default instance from remote computer

I installed SQL2005 as default instance.
After that I installed SQL2000 with instance name "SQL2K". Then I installed
SP4.
I can'not connect to SQL2K instance from remote machine. But if I log on at
machine on which SQL Server installed I can connect to instance.
And I can connect to default instance (SQL2005) from remote machine.
How to solve this problem?Is the SQL Server Browser service running? It helps resolve names of named
instances to the port number. Since SQL Server 2005 is the default instance,
it is probably using port 1433. Therefore SQL Server 2000 must be using some
other port, but you don't know which port, but the SQL Server Browser
service will know.
--
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Alexey Rokhin" <ar@.hotmail.com> wrote in message
news:%23PF4wc16FHA.1416@.TK2MSFTNGP09.phx.gbl...
>I installed SQL2005 as default instance.
> After that I installed SQL2000 with instance name "SQL2K". Then I
> installed SP4.
> I can'not connect to SQL2K instance from remote machine. But if I log on
> at machine on which SQL Server installed I can connect to instance.
> And I can connect to default instance (SQL2005) from remote machine.
> How to solve this problem?
>

can not access clustering SQL Server after relocation

Hi all:

I have a clustering SQL Server on Node1 and Node2, the Node1 has named
Instance1 and Node2 has named Instance2, no default instance. We
tested it that everthing is OK, then we decide to move to DR location.

The relocation kept the same virtual and phusical server name, and we
did not change SQL Server server network utility. But server IP
addresses were changed(vitual and physical). We can start the
clustering SQL Server as before, and everything looks like well.

However the users can not access it remotely, and they did not change
the client network utility. But if I login the server,I can access it
from Query Analyzer even though ther is not client network utility
setup on the server. I can ping the vitual server name, how can I make
sure the ports are working well? (We did not use the default port for
named instance).

I remember I did input the virtual server IP address when I installed
the clustering SQL Server. Of course, it was change after relocation.
Is it the reason for failed remote login? If it is, how to fix it?

Does anyboday know there is document for clustering SQL Server
relocation?

Thanks
Williew2jin@.hotmail.com (willie) wrote in message news:<6610106b.0408251200.14624760@.posting.google.com>...
> Hi all:
> I have a clustering SQL Server on Node1 and Node2, the Node1 has named
> Instance1 and Node2 has named Instance2, no default instance. We
> tested it that everthing is OK, then we decide to move to DR location.
> The relocation kept the same virtual and phusical server name, and we
> did not change SQL Server server network utility. But server IP
> addresses were changed(vitual and physical). We can start the
> clustering SQL Server as before, and everything looks like well.
> However the users can not access it remotely, and they did not change
> the client network utility. But if I login the server,I can access it
> from Query Analyzer even though ther is not client network utility
> setup on the server. I can ping the vitual server name, how can I make
> sure the ports are working well? (We did not use the default port for
> named instance).
> I remember I did input the virtual server IP address when I installed
> the clustering SQL Server. Of course, it was change after relocation.
> Is it the reason for failed remote login? If it is, how to fix it?
> Does anyboday know there is document for clustering SQL Server
> relocation?
> Thanks
> Willie

This article might help:

http://support.microsoft.com/defaul...8&Product=sql2k

Simon

can not access clustering SQL Server after relocation

Hi all:
I have a clustering SQL Server on Node1 and Node2, the Node1 has named
Instance1 and Node2 has named Instance2, no default instance. We
tested it that everthing is OK, then we decide to move to DR location.
The relocation kept the same virtual and phusical server name, and we
did not change SQL Server server network utility. But server IP
addresses were changed(vitual and physical). We can start the
clustering SQL Server as before, and everything looks like well.
However the users can not access it remotely, and they did not change
the client network utility. But if I login the server,I can access it
from Query Analyzer even though ther is not client network utility
setup on the server. I can ping the vitual server name, how can I make
sure the ports are working well? (We did not use the default port for
named instance).
I remember I did input the virtual server IP address when I installed
the clustering SQL Server. Of course, it was change after relocation.
Is it the reason for failed remote login? If it is, how to fix it?
Does anyboday know there is document for clustering SQL Server
relocation?
Thanks
Williew2jin@.hotmail.com (willie) wrote in message news:<6610106b.0408251200.14624760@.posting.googl
e.com>...
> Hi all:
> I have a clustering SQL Server on Node1 and Node2, the Node1 has named
> Instance1 and Node2 has named Instance2, no default instance. We
> tested it that everthing is OK, then we decide to move to DR location.
> The relocation kept the same virtual and phusical server name, and we
> did not change SQL Server server network utility. But server IP
> addresses were changed(vitual and physical). We can start the
> clustering SQL Server as before, and everything looks like well.
> However the users can not access it remotely, and they did not change
> the client network utility. But if I login the server,I can access it
> from Query Analyzer even though ther is not client network utility
> setup on the server. I can ping the vitual server name, how can I make
> sure the ports are working well? (We did not use the default port for
> named instance).
> I remember I did input the virtual server IP address when I installed
> the clustering SQL Server. Of course, it was change after relocation.
> Is it the reason for failed remote login? If it is, how to fix it?
> Does anyboday know there is document for clustering SQL Server
> relocation?
> Thanks
> Willie
This article might help:
http://support.microsoft.com/defaul...8&Product=sql2k
Simon

can not access clustering SQL Server after relocation

Hi all:
I have a clustering SQL Server on Node1 and Node2, the Node1 has named
Instance1 and Node2 has named Instance2, no default instance. We
tested it that everthing is OK, then we decide to move to DR location.
The relocation kept the same virtual and phusical server name, and we
did not change SQL Server server network utility. But server IP
addresses were changed(vitual and physical). We can start the
clustering SQL Server as before, and everything looks like well.
However the users can not access it remotely, and they did not change
the client network utility. But if I login the server,I can access it
from Query Analyzer even though ther is not client network utility
setup on the server. I can ping the vitual server name, how can I make
sure the ports are working well? (We did not use the default port for
named instance).
I remember I did input the virtual server IP address when I installed
the clustering SQL Server. Of course, it was change after relocation.
Is it the reason for failed remote login? If it is, how to fix it?
Does anyboday know there is document for clustering SQL Server
relocation?
Thanks
Williew2jin@.hotmail.com (willie) wrote in message news:<6610106b.0408251200.14624760@.posting.google.com>...
> Hi all:
> I have a clustering SQL Server on Node1 and Node2, the Node1 has named
> Instance1 and Node2 has named Instance2, no default instance. We
> tested it that everthing is OK, then we decide to move to DR location.
> The relocation kept the same virtual and phusical server name, and we
> did not change SQL Server server network utility. But server IP
> addresses were changed(vitual and physical). We can start the
> clustering SQL Server as before, and everything looks like well.
> However the users can not access it remotely, and they did not change
> the client network utility. But if I login the server,I can access it
> from Query Analyzer even though ther is not client network utility
> setup on the server. I can ping the vitual server name, how can I make
> sure the ports are working well? (We did not use the default port for
> named instance).
> I remember I did input the virtual server IP address when I installed
> the clustering SQL Server. Of course, it was change after relocation.
> Is it the reason for failed remote login? If it is, how to fix it?
> Does anyboday know there is document for clustering SQL Server
> relocation?
> Thanks
> Willie
This article might help:
http://support.microsoft.com/default.aspx?scid=kb;en-us;319578&Product=sql2k
Simonsql

can not access clustering SQL Server after relocation

Hi all:
I have a clustering SQL Server on Node1 and Node2, the Node1 has named
Instance1 and Node2 has named Instance2, no default instance. We
tested it that everthing is OK, then we decide to move to DR location.
The relocation kept the same virtual and phusical server name, and we
did not change SQL Server server network utility. But server IP
addresses were changed(vitual and physical). We can start the
clustering SQL Server as before, and everything looks like well.
However the users can not access it remotely, and they did not change
the client network utility. But if I login the server,I can access it
from Query Analyzer even though ther is not client network utility
setup on the server. I can ping the vitual server name, how can I make
sure the ports are working well? (We did not use the default port for
named instance).
I remember I did input the virtual server IP address when I installed
the clustering SQL Server. Of course, it was change after relocation.
Is it the reason for failed remote login? If it is, how to fix it?
Does anyboday know there is document for clustering SQL Server
relocation?
Thanks
Willie
w2jin@.hotmail.com (willie) wrote in message news:<6610106b.0408251200.14624760@.posting.google. com>...
> Hi all:
> I have a clustering SQL Server on Node1 and Node2, the Node1 has named
> Instance1 and Node2 has named Instance2, no default instance. We
> tested it that everthing is OK, then we decide to move to DR location.
> The relocation kept the same virtual and phusical server name, and we
> did not change SQL Server server network utility. But server IP
> addresses were changed(vitual and physical). We can start the
> clustering SQL Server as before, and everything looks like well.
> However the users can not access it remotely, and they did not change
> the client network utility. But if I login the server,I can access it
> from Query Analyzer even though ther is not client network utility
> setup on the server. I can ping the vitual server name, how can I make
> sure the ports are working well? (We did not use the default port for
> named instance).
> I remember I did input the virtual server IP address when I installed
> the clustering SQL Server. Of course, it was change after relocation.
> Is it the reason for failed remote login? If it is, how to fix it?
> Does anyboday know there is document for clustering SQL Server
> relocation?
> Thanks
> Willie
This article might help:
http://support.microsoft.com/default...&Product=sql2k
Simon

can not access clustering SQL Server after relocation

Hi all:
I have a clustering SQL Server on Node1 and Node2, the Node1 has named
Instance1 and Node2 has named Instance2, no default instance. We
tested it that everthing is OK, then we decide to move to DR location.
The relocation kept the same virtual and phusical server name, and we
did not change SQL Server server network utility. But server IP
addresses were changed(vitual and physical). We can start the
clustering SQL Server as before, and everything looks like well.
However the users can not access it remotely, and they did not change
the client network utility. But if I login the server,I can access it
from Query Analyzer even though ther is not client network utility
setup on the server. I can ping the vitual server name, how can I make
sure the ports are working well? (We did not use the default port for
named instance).
I remember I did input the virtual server IP address when I installed
the clustering SQL Server. Of course, it was change after relocation.
Is it the reason for failed remote login? If it is, how to fix it?
Does anyboday know there is document for clustering SQL Server
relocation?
Thanks
Willie
w2jin@.hotmail.com (willie) wrote in message news:<6610106b.0408251200.14624760@.posting.google. com>...
> Hi all:
> I have a clustering SQL Server on Node1 and Node2, the Node1 has named
> Instance1 and Node2 has named Instance2, no default instance. We
> tested it that everthing is OK, then we decide to move to DR location.
> The relocation kept the same virtual and phusical server name, and we
> did not change SQL Server server network utility. But server IP
> addresses were changed(vitual and physical). We can start the
> clustering SQL Server as before, and everything looks like well.
> However the users can not access it remotely, and they did not change
> the client network utility. But if I login the server,I can access it
> from Query Analyzer even though ther is not client network utility
> setup on the server. I can ping the vitual server name, how can I make
> sure the ports are working well? (We did not use the default port for
> named instance).
> I remember I did input the virtual server IP address when I installed
> the clustering SQL Server. Of course, it was change after relocation.
> Is it the reason for failed remote login? If it is, how to fix it?
> Does anyboday know there is document for clustering SQL Server
> relocation?
> Thanks
> Willie
This article might help:
http://support.microsoft.com/default...&Product=sql2k
Simon

Can isolation level be set in connectionstring?

Hi,

I would like to be able to alter the default isolation level at connection time via the ADO connection string. Can this be done?

Why? I have various reporting applications (Crystal etc.) that queries against MS SQL server using ADO (SQLOLEDB). I would like to be able to alter the isolation level for these queries to readuncommitted. But many of the reporting applications does not have this option and they autogenerate the SQL making it impossible to use the use the WITH(table_hints) clause in the SELECT statement. So if I could set the isolation level in the connection string this could be a workaround.

Any help will be appreciated!

Bertrand

No, not in the connection string.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Can isolation level be set in connectionstring?

Hi,

I would like to be able to alter the default isolation level at connection time via the ADO connection string. Can this be done?

Why? I have various reporting applications (Crystal etc.) that queries against MS SQL server using ADO (SQLOLEDB). I would like to be able to alter the isolation level for these queries to readuncommitted. But many of the reporting applications does not have this option and they autogenerate the SQL making it impossible to use the use the WITH(table_hints) clause in the SELECT statement. So if I could set the isolation level in the connection string this could be a workaround.

Any help will be appreciated!

Bertrand

No, not in the connection string.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Can I use my own Stored Procedure template with SQL2005?

When I go to create a new stored procedure, function, etc. I get a default template... is there anyway to replace this template with one of my own? One that will already have the important information pre-populated (the stuff I always end up having to type in, like company name, etc.).

Hi,

in SQL Server Management Studio, choose View -> Template Explorer. (Or Ctrl + Alt + T). There you can manage templates. Edit them whatsoever.

Can I use MSDE in a Microsoft's Corporate Client

I Work in a Corporation where SQL is not an standard to deploy but office 2000 are desktop utilities by default. They use access, word, excell, etc to work. Can I use MSDE with Vb 6 and how can I administer the MSDE database ? I have seen Access frontend
to make changes and permisions and its very poor. Can I use Sql Server Console or Third parts ?
Thanks
hi,
"Designer improving costs" <janou_dank@.yahoo.com.ar> ha scritto nel
messaggio news:F799D60E-DC43-480E-BE57-6EC9E7C02B47@.microsoft.com...
> I Work in a Corporation where SQL is not an standard to deploy but office
2000 are desktop utilities
>by default. They use access, word, excell, etc to work. Can I use MSDE with
Vb 6 and how can I
>administer the MSDE database ? I have seen Access frontend to make changes
and permisions and
>its very poor. Can I use Sql Server Console or Third parts ?
> Thanks
you can download and install MSDE for sure in corporate environments, as
MSDE release A (http://www.microsoft.com/sql/msde/do...s/download.asp) is
free..
as regard management, you can use SQL Server management tools like
Enterprise Manager and Query Analyzer only if you a licensed owner of a full
SQL Server edition, but you can write your own tool, use Acces and/or resort
to third parties tools like those provided at
http://www.microsoft.com/sql/msde/partners/default.asp and/or
http://www.aspfaq.com/show.asp?id=2442
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||If you have licensed SQL Server ownership with which the tools are
available, you can use the tools to manage the MSDE installations.

can i use a store procedure as default value for a column?

Is it possible to use a stored procedure to fill the default value of a column when i'm building the db?

i mean if i can use a stored procedure for the "colum property": "default value or bnding"

if yes how can i do it?

No, you won't be able to specify a stored procedure in your table definition as a default value for a column. Your best bet for this is to set up a trigger (either AFTER or INSTEAD OF) to enforce the default value.

|||

You can, however, use a scalar user-defined function as the default value. So if you can convert the sproc to a UDF or call it from one, you're good to go.

Don

can I use * to specify 'Output Column' for OLD DB Source Editor?

I am working on a situation similar to 'Get all from Table A that isn't in Table B' http://www.sqlis.com/default.aspx?311

I noticed that if one column's name of source table changes,(say Year to Year2) I have to modify all 'data flow transformations' in the task.

I am new to SSIS.

thanks! -ZZ

ZZhang wrote:

I am working on a situation similar to 'Get all from Table A that isn't in Table B' http://www.sqlis.com/default.aspx?311

I noticed that if one column's name of source table changes,(say Year to Year2) I have to modify all 'data flow transformations' in the task.

I am new to SSIS.

thanks! -ZZ

You could use '*' if you wanted but this is about as bad as bad practice gets. Don't do it. If the name of a column changes then SSIS will break because it stored the metadata of the external data source. This is by design.

-Jamie

|||

Hi, Jamie,
Thanks so much for your quick response! I have two questions then.

1. How to use * ? I can not find it in the 'OLD DB Source Editor'.

2. Let me simplifing my case. I have a remote source table ( which has may columns, incluing 'ID' and 'Date'). The schema may change, but not 'ID' and 'Date' columns. The DTS job is to get all rows ( select * from myTable where [Date] = getdate() ), and output to a delimited flat file.

What is the best practice SSIS for this case?

Thanks again!

-ZZ

|||

Like I said. You can't do it. If the external metadata changes then your data-flow will error.

-Jamie

|||

thanks, Jamie!

Honestly, this surprised me, if it can not use *. I will choose NOT to use SSIS for my simple job, because it does not make sense to modify ( and test) SSIS package every time the schema changes. I hope there is a workaround to meet my job requirement in SSIS.

-ZZ

|||

What? Your problem is the fact that your schema is changing, not that SSIS can't handle it. Are you saying that its impossible to know what your schema will look like from one day to the next? I've never seen a company that would run its systems like that nor would i want to.

Sorry to sound rude but it just sounds crazy to me!

-Jamie

|||

Thanks Jamie for your time to answer my question!

I am new to SSIS, and have not used variable, expression, and sricpt much. I am open-mind, and believe there is a way (simple or difficult), to solve my issue. Maybe you are right, but here I am searching 'how-to' solution, like ( select * from MyTable). Should I use *? it is another question.

Thanks again!

-ZZhang

|||

Again,

Yes you can use "SELECT * FROM MyTable"|||

It seems that MS has solution for 'Dynamic Metadata', although SSIS pipeline requires static metadata.

"Advacned ETL: Embedding Integration Services" from PDC05 mentioned this issue. SMO is needed.

I am still searching for the samples.

-ZZhang

can I use * to specify 'Output Column' for OLD DB Source Editor?

I am working on a situation similar to 'Get all from Table A that isn't in Table B' http://www.sqlis.com/default.aspx?311

I noticed that if one column's name of source table changes,(say Year to Year2) I have to modify all 'data flow transformations' in the task.

I am new to SSIS.

thanks! -ZZ

ZZhang wrote:

I am working on a situation similar to 'Get all from Table A that isn't in Table B' http://www.sqlis.com/default.aspx?311

I noticed that if one column's name of source table changes,(say Year to Year2) I have to modify all 'data flow transformations' in the task.

I am new to SSIS.

thanks! -ZZ

You could use '*' if you wanted but this is about as bad as bad practice gets. Don't do it. If the name of a column changes then SSIS will break because it stored the metadata of the external data source. This is by design.

-Jamie

|||

Hi, Jamie,
Thanks so much for your quick response! I have two questions then.

1. How to use * ? I can not find it in the 'OLD DB Source Editor'.

2. Let me simplifing my case. I have a remote source table ( which has may columns, incluing 'ID' and 'Date'). The schema may change, but not 'ID' and 'Date' columns. The DTS job is to get all rows ( select * from myTable where [Date] = getdate() ), and output to a delimited flat file.

What is the best practice SSIS for this case?

Thanks again!

-ZZ

|||

Like I said. You can't do it. If the external metadata changes then your data-flow will error.

-Jamie

|||

thanks, Jamie!

Honestly, this surprised me, if it can not use *. I will choose NOT to use SSIS for my simple job, because it does not make sense to modify ( and test) SSIS package every time the schema changes. I hope there is a workaround to meet my job requirement in SSIS.

-ZZ

|||

What? Your problem is the fact that your schema is changing, not that SSIS can't handle it. Are you saying that its impossible to know what your schema will look like from one day to the next? I've never seen a company that would run its systems like that nor would i want to.

Sorry to sound rude but it just sounds crazy to me!

-Jamie

|||

Thanks Jamie for your time to answer my question!

I am new to SSIS, and have not used variable, expression, and sricpt much. I am open-mind, and believe there is a way (simple or difficult), to solve my issue. Maybe you are right, but here I am searching 'how-to' solution, like ( select * from MyTable). Should I use *? it is another question.

Thanks again!

-ZZhang

|||

Again,

Yes you can use "SELECT * FROM MyTable"|||

It seems that MS has solution for 'Dynamic Metadata', although SSIS pipeline requires static metadata.

"Advacned ETL: Embedding Integration Services" from PDC05 mentioned this issue. SMO is needed.

I am still searching for the samples.

-ZZhang

Can I Turn off Auto Execution of Report when all parameters have default values?

My situation....

I deploy a report in Report Server. Ther report has 5-10 parameters. When I design the report, I supply a default value for each parameter, similiar to the "Add a select all option" tutorials.

So I end up with defaults like "Select a Project Manager", "Select a Fiscal Year", etc... I use dynamic queries to read the parameters and insert the appropriate logic into the where string of my main dataset. If the user selects a value from my parameter lists, I append a clause to the SQL string, if they choose the default option, I ignore the parameter, and that effectively returns all of the records (like Select * from ....)

My Issue...

When I provide a default paramater for ALL of the parameters available, the report auto-executes when the user picks it from the folder, and isn;t given the opportunity to refine the default criteria I have provided.

My Question....

Is there any way to turn the autoexecution off?

Thanks for any help...

There is no method to turn off the auto execution of the report if all parameters have default values.

As you have probable already found out, you can populate all but one of the parameters to get the result you desire. But that makes the user have to supply a value of the parameter.

Can I still redistribute MSDE after SQL Express is out?

I wonder if I can still redistribute MSDE after SQL Express is released. I
read in this page http://lab.msdn.microsoft.com/express/faq/default.aspx that
SQL Server Express is the replacement of MSDE. So, I wonder if the
redistributable license for MSDE is still valid after SQL Server Express is
out..?
Thanks,
Don't see why not, as you can still distribute MSDE 1.0 apps even though
MSDE 2000 is its "replacement"...
http://www.aspfaq.com/
(Reverse address to reply.)
"Hani Atassi" <hani@.community.nospam> wrote in message
news:82682AA8-A5C9-405E-B809-A2A051A7485C@.microsoft.com...
> I wonder if I can still redistribute MSDE after SQL Express is released. I
> read in this page http://lab.msdn.microsoft.com/express/faq/default.aspx
that
> SQL Server Express is the replacement of MSDE. So, I wonder if the
> redistributable license for MSDE is still valid after SQL Server Express
is
> out..?
> Thanks,
>
|||yes
the support lifecycles of these things will overlap by at least 2 years,
according to the stated MS support lifecycle policy.
-D
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:eefJw1dxEHA.1196@.TK2MSFTNGP15.phx.gbl...
> Don't see why not, as you can still distribute MSDE 1.0 apps even though
> MSDE 2000 is its "replacement"...
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Hani Atassi" <hani@.community.nospam> wrote in message
> news:82682AA8-A5C9-405E-B809-A2A051A7485C@.microsoft.com...
> that
> is
>

Can I set a default range for the identity values for merge replication?

Hello,

We have a couple of tables that can have quite a bit of data each day prior to replication. Can we increase the default values for a table for each subscription? For example we have a table called table1 and on the sqlexpress client they could enter in 10000 rows a day, on table2 it's just 100 rows a day. How can we increase the values to where we do not get the error for table1 stating that the insert failed because it conflicted with the identity range check constraint. Thanks in advance.

Hi, John

If I understand correctly, you actually want to set different identityrange from different article. For example, table1 identity range is 10,000 and table2 with identity range is 1,000. You can set it through sp_addmergearticle with control values of @.identityrangemanagementoption, @.pub_identity_range, and @.identity_range.

BTW, you are not allowed to set different identity range for different subscriptions which subscribe to the same publication.

Hope these information will help.

Thanks

Yunjing

Can I just make the necessary registry changes to turn on error reporting in SQL2000 SP3

http://support.microsoft.com/default...b;en-us;328446
The part that describes how to turn off Error Reporting for a default =
instance is unclear in this article. It looks to be missing stuff. So =
maybe all I have to do to enable Error Reporting, is to manually make =
the change in the registry. That way if I want to turn it off I just =
change 1 to 0 as is in the article. Is that OK will that be sufficient? =
Thanks.
--=20
George Hester
__________________________________
You are correct that the artilce is missing something. The proper method to
enable this is as follows:
To turn on error reporting by using SQL Server Enterprise
Manager or Analysis Manager, follow these steps:
1. Click to select the name of the server.
2. Right-click the server name, and then click Properties.
3. Click to select the Enable Error Reporting Feature check box.
It is always best to use the interface than to manually edit the registry.
Thanks for the catch. I am getting the article updated.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Oh cool yeah I'd rather do it that way. Thanks.
--=20
George Hester
__________________________________
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message =
news:#PLYRQnPEHA.1516@.cpmsftngxa10.phx.gbl...
> You are correct that the artilce is missing something. The proper =
method to=20
> enable this is as follows:
>=20
> To turn on error reporting by using SQL Server Enterprise
> Manager or Analysis Manager, follow these steps:
>=20
> 1. Click to select the name of the server.
> 2. Right-click the server name, and then click Properties.
> 3. Click to select the Enable Error Reporting Feature check box.
>=20
> It is always best to use the interface than to manually edit the =
registry.
>=20
> Thanks for the catch. I am getting the article updated.
>=20
> Rand
> This posting is provided "as is" with no warranties and confers no =
rights.
>

Can I just make the necessary registry changes to turn on error reporting in SQL2000 SP3

http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;328446
The part that describes how to turn off Error Reporting for a default = instance is unclear in this article. It looks to be missing stuff. So = maybe all I have to do to enable Error Reporting, is to manually make = the change in the registry. That way if I want to turn it off I just = change 1 to 0 as is in the article. Is that OK will that be sufficient? = Thanks.
-- George Hester
__________________________________You are correct that the artilce is missing something. The proper method to
enable this is as follows:
To turn on error reporting by using SQL Server Enterprise
Manager or Analysis Manager, follow these steps:
1. Click to select the name of the server.
2. Right-click the server name, and then click Properties.
3. Click to select the Enable Error Reporting Feature check box.
It is always best to use the interface than to manually edit the registry.
Thanks for the catch. I am getting the article updated.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Oh cool yeah I'd rather do it that way. Thanks.
-- George Hester
__________________________________
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message =news:#PLYRQnPEHA.1516@.cpmsftngxa10.phx.gbl...
> You are correct that the artilce is missing something. The proper =method to > enable this is as follows:
> > To turn on error reporting by using SQL Server Enterprise
> Manager or Analysis Manager, follow these steps:
> > 1. Click to select the name of the server.
> 2. Right-click the server name, and then click Properties.
> 3. Click to select the Enable Error Reporting Feature check box.
> > It is always best to use the interface than to manually edit the =registry.
> > Thanks for the catch. I am getting the article updated.
> > Rand
> This posting is provided "as is" with no warranties and confers no =rights.
>

Can I just make the necessary registry changes to turn on error reporting in SQL2000 S

http://support.microsoft.com/defaul...kb;en-us;328446
The part that describes how to turn off Error Reporting for a default =
instance is unclear in this article. It looks to be missing stuff. So =
maybe all I have to do to enable Error Reporting, is to manually make =
the change in the registry. That way if I want to turn it off I just =
change 1 to 0 as is in the article. Is that OK will that be sufficient? =
Thanks.
--=20
George Hester
__________________________________You are correct that the artilce is missing something. The proper method to
enable this is as follows:
To turn on error reporting by using SQL Server Enterprise
Manager or Analysis Manager, follow these steps:
1. Click to select the name of the server.
2. Right-click the server name, and then click Properties.
3. Click to select the Enable Error Reporting Feature check box.
It is always best to use the interface than to manually edit the registry.
Thanks for the catch. I am getting the article updated.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Oh cool yeah I'd rather do it that way. Thanks.
--=20
George Hester
__________________________________
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message =
news:#PLYRQnPEHA.1516@.cpmsftngxa10.phx.gbl...
> You are correct that the artilce is missing something. The proper =
method to=20
> enable this is as follows:
>=20
> To turn on error reporting by using SQL Server Enterprise
> Manager or Analysis Manager, follow these steps:
>=20
> 1. Click to select the name of the server.
> 2. Right-click the server name, and then click Properties.
> 3. Click to select the Enable Error Reporting Feature check box.
>=20
> It is always best to use the interface than to manually edit the =
registry.
>=20
> Thanks for the catch. I am getting the article updated.
>=20
> Rand
> This posting is provided "as is" with no warranties and confers no =
rights.
>