Replication: SQL Server

I found the following article about how to create Transactional replication without Initial snapshot but i am not very sure how we can do that. If someone has done this already could you please help me out here.

Our database is really big (Abt 200+ GB) and its on SQL Server 2005. We already have Transactional replication setup (pull subsc) via normal method like create publication and then initialize with Snapshot.. which takes overall 7 Hrs.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

i've done it
basically, if you are able to copy the database yourself, you don't need to use the snapshot,
you just make the copy and then tell sql server not to perform the snapshot,
but you must take into account that the databases must be identical when sql server starts the replication process.
in order to achieve that, you will need to suspend the update activity against your source envrionement

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
AanvikAuthor Commented:
Thank you for your response.

So it means that
1.Stop all the db activity...
2 take backup..
3.copy and restore to reporting server
4.Configure distribution on reporting server
5. dont configure snapshot on Prod server
6. Configure subscription on reporting server

Am I going in correct direction... Also If yes then doing this backup/copy and Restore will take abt 4 hrs and its better to generate snapshot in 3 hrs in this case if you have to keep the application down against the database.

Also can we do the same with GUI interface..


you caN do everything using the gui

basically you are in the right direction, in order to tell sql server not to use a snapshot, you need to define everything regulary through the gui, and just unmark the perform snapshot in the wizard
but basically, you will need to make sure the database are identical before the replication starts, otherwise you might encounter errors
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

AanvikAuthor Commented:
Hi Shalom,
Thank you for your comments. But as I said backup/Copy to Reporting server/Restore will take about 4 hrs and we can;t keep the application down for 4 hrs.. Its better to create snapshot in this case cause it takes about 3 hrs...  

>>but basically, you will need to make sure the database are identical before the replication starts, otherwise you might encounter errors

Regarding this above comments do you mean just the structure or data as well?
structure and data
AanvikAuthor Commented:
Its not completely answered but helped me getting into right direction.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.