Can't copy/export a database with identity *NEWBIE*

I have a database where some tables have the IDENTITY = YES.
If I copy or export from ServerA to ServerB, the IDENTITY gets set to No.
This has to be a simple problem.
How is it fixed?
If you are simply doing an export/import you need to create the table with
the desired format on the subscriber/destination/target side - i.e. with the
identity property on the column. Then before you do your import set
identity_insert on for that table, i.e.
SET IDENTITY_INSERT MyTableName ONIf you are using bcp use the -E parameter.
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
"Jeffrey Brandt" <jdbrandt@.verizon.net> wrote in message
news:lO7fi.268$XH5.206@.trndny02...
>I have a database where some tables have the IDENTITY = YES.
> If I copy or export from ServerA to ServerB, the IDENTITY gets set to No.
> This has to be a simple problem.
> How is it fixed?
>
|||You were SOO right.
I ended up using snapshot replication, and pushed it to the other machine.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OBM0x%23YtHHA.1728@.TK2MSFTNGP06.phx.gbl...
> You can use queued updating subscribers or merge replication both with
> automatic identity range management.
> HTH,
> Paul Ibison
>

Cant Connect to Sql Server

Warning extreme newbie.

I am trying to follow a .Net Walk Thru that connects to Sql Server. The SqlConnection, SqlDataAdapter, and DataSet all appear to be working properly, but when the web page opens I get a 'Sql Server Does Not Exist or Access Denied.'

Any ideas would be greatly apprieciated.

fryer

Is the connection string correct (i.e. username, password, server address, etc.) and do you have the correct permissions to access the database?

Ryan|||

Connection Strings: I have used the one generated with the SqlConnection Object and I have modified it many different ways. Integrated Security on & off, By Server name/IP Address. Using a port number & using TCIP/IP. I have also tried my connecting to my local computer and the office server.

Database: I definitely have rights to the database.

Could the problem be how it is connecting, some sort of port disconnect? Could something be overriding my connection string?

Thanks.

fryere

Can't connect to server - real newbie here

SLQ 2000, Win XP Pro network
I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall turned
off)
The SQL server seems to be running fine in that I can access the default
tables from the local computer. The problem is, I can't connect to the SLQ
Server from another XP Pro client computer using Enterprise Manager. That
is, I can't register it. I get a "server does not exist" error.
I've tried both Windows authentication and SQL Server authentication. To
use SQL auth. I'm assuming that all I have to do is create a new login on
the server, which I have done. I've made sure this login is an administrator
with ownership and public rights to each database.
What else should I check or setup?
All help greatly appreciated!!
Karl wrote:
> SLQ 2000, Win XP Pro network
> I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall
> turned off)
> The SQL server seems to be running fine in that I can access the
> default tables from the local computer. The problem is, I can't
> connect to the SLQ Server from another XP Pro client computer using
> Enterprise Manager. That is, I can't register it. I get a "server
> does not exist" error.
> I've tried both Windows authentication and SQL Server authentication.
> To use SQL auth. I'm assuming that all I have to do is create a new
> login on the server, which I have done. I've made sure this login is
> an administrator with ownership and public rights to each database.
> What else should I check or setup?
> All help greatly appreciated!!
What name are you using for the SQL Server? Can you see the other PC on
the network. Try using the IP address in case the name is not resolving
properly.
David Gugick
Imceda Software
www.imceda.com
|||Thank you for the reply.
As it turns out, I was trying this on a new installation of XP Pro running
SP 2 as I mentioned. As soon as I updated SQL 2000 with its service pack 3,
I was able to connect to the server from the client computers. Leave it to
my 14 year old son to suggest this solution. :-)
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:eR5zVb84EHA.3596@.TK2MSFTNGP12.phx.gbl...
> Karl wrote:
> What name are you using for the SQL Server? Can you see the other PC on
> the network. Try using the IP address in case the name is not resolving
> properly.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>

Can't connect to server - real newbie here

SLQ 2000, Win XP Pro network
I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall turned
off)
The SQL server seems to be running fine in that I can access the default
tables from the local computer. The problem is, I can't connect to the SLQ
Server from another XP Pro client computer using Enterprise Manager. That
is, I can't register it. I get a "server does not exist" error.
I've tried both Windows authentication and SQL Server authentication. To
use SQL auth. I'm assuming that all I have to do is create a new login on
the server, which I have done. I've made sure this login is an administrator
with ownership and public rights to each database.
What else should I check or setup?
All help greatly appreciated!!Karl wrote:
> SLQ 2000, Win XP Pro network
> I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall
> turned off)
> The SQL server seems to be running fine in that I can access the
> default tables from the local computer. The problem is, I can't
> connect to the SLQ Server from another XP Pro client computer using
> Enterprise Manager. That is, I can't register it. I get a "server
> does not exist" error.
> I've tried both Windows authentication and SQL Server authentication.
> To use SQL auth. I'm assuming that all I have to do is create a new
> login on the server, which I have done. I've made sure this login is
> an administrator with ownership and public rights to each database.
> What else should I check or setup?
> All help greatly appreciated!!
What name are you using for the SQL Server? Can you see the other PC on
the network. Try using the IP address in case the name is not resolving
properly.
--
David Gugick
Imceda Software
www.imceda.com|||Thank you for the reply.
As it turns out, I was trying this on a new installation of XP Pro running
SP 2 as I mentioned. As soon as I updated SQL 2000 with its service pack 3,
I was able to connect to the server from the client computers. Leave it to
my 14 year old son to suggest this solution. :-)
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:eR5zVb84EHA.3596@.TK2MSFTNGP12.phx.gbl...
> Karl wrote:
> > SLQ 2000, Win XP Pro network
> >
> > I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall
> > turned off)
> >
> > The SQL server seems to be running fine in that I can access the
> > default tables from the local computer. The problem is, I can't
> > connect to the SLQ Server from another XP Pro client computer using
> > Enterprise Manager. That is, I can't register it. I get a "server
> > does not exist" error.
> >
> > I've tried both Windows authentication and SQL Server authentication.
> > To use SQL auth. I'm assuming that all I have to do is create a new
> > login on the server, which I have done. I've made sure this login is
> > an administrator with ownership and public rights to each database.
> >
> > What else should I check or setup?
> >
> > All help greatly appreciated!!
> What name are you using for the SQL Server? Can you see the other PC on
> the network. Try using the IP address in case the name is not resolving
> properly.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>