Backup publisher DB

Can I make a backup of my Publisher DB and then restore it on the
Subscriber, or this operation can generate problems?
Marco,
if you are using sql server 2005 you can use the option to "initialize with
backup". If not then you can do a nosync initialization. Once done, you'll
need to remove identity attributes for a nosync initialization.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Yes, but on SQL 2000 you need to make the identity columns, triggers and
constraints Not For Replication.
Hilary Cotter
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
"Marco" <peska78@.tin.it> wrote in message
news:1172491146.648730.117190@.k78g2000cwa.googlegr oups.com...
> Can I make a backup of my Publisher DB and then restore it on the
> Subscriber, or this operation can generate problems?
>
|||Tanks for your answers.
I'm using SQL 2000; I have not understood very well the correct
procedure.
I have only few tables, every table has a unique identifier, no
dependencies, no idexes, no triggers.
If simply I export all data in tables, for example in .txt files, and
then I reimport the data in the other DB?

Backup in SQL 7.0 and restored in SQL 2000

Hello: I have made backup of a data base in SQL 7.0 and I have been able it to recover in a SQL 2000 without problems, can this generate some kind to me of later problem in this restored database?You should be fine with the method you have chosen but you may have problems with logins. Also, double-check to make sure that customized objects have been restored as well - e.g. stored procedures, jobs, dts scripts ...

Check out the following article:

article1 (http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q246133&ID=KB;EN-US;Q246133&)

For an excellent in-depth article discussing moving databases from 7 to 2000, check out the following article - part 2 is more specific:

article2 (http://www.sqlteam.com/item.asp?ItemID=9066)|||For the login issues run SP_CHANGE_USERS_LOGIN REPORT which reports orphaned users and run WITH AUTO_FIX to fix the logins, refer to BOL for more information.

HTH