 |
SQL Server 2008 General discussion of SQL Server *2008* version only - not related to a specific book. |
Welcome to the p2p.wrox.com Forums.
You are currently viewing the SQL Server 2008 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
|
|
|

March 26th, 2015, 12:56 PM
|
Friend of Wrox
|
|
Join Date: Jun 2003
Posts: 428
Thanks: 57
Thanked 2 Times in 2 Posts
|
|
Copy ENTIRE database including table contents and user ids
Perhaps I'm just not searching using the right keywords, but is there really no SIMPLE way to copy an entire SQL Server database from one server to another, including: - ALL tables
- Primary keys, indices, identity specifications and any other settings not specifically listed here but whose oimission cause problems
- Complete table contents
- ALL views created as actual VIEWS instead of changing them to tables (Why would I ever want a view converted to a table, MS?)
- ALL Stored Procedures
- ALL Functions
- ALL Users
- At the server level if they do not already exist there
- Then foir the database with all the same permissions granted automatically
- And any other database objects or features not explicitly listed here but which I might need in order to reproduce some problem in production in our test environment?
|

March 26th, 2015, 02:57 PM
|
Friend of Wrox
|
|
Join Date: Jul 2003
Posts: 599
Thanks: 6
Thanked 3 Times in 3 Posts
|
|
Full backup should have all of that
|

March 26th, 2015, 03:41 PM
|
Friend of Wrox
|
|
Join Date: Jun 2003
Posts: 428
Thanks: 57
Thanked 2 Times in 2 Posts
|
|
Not an option.
Any other suggestions?
|

March 26th, 2015, 07:22 PM
|
Friend of Wrox
|
|
Join Date: Jan 2004
Posts: 1,870
Thanks: 12
Thanked 20 Times in 20 Posts
|
|
I have been told this before. No you cant create a .bak file, even if you could you cant restore it...... This is the easiest option for you. Someone has this access and can do it. It took me a few weeks but I did manage to email the right people and get it done in the end.
No other option I am aware of. Whoever has given you this requirement with such restrictions has unrealistic business expectations.
I use SQLServer TableDiff to move data from one instance to another. You do have this option available on 2008 but it will not move everything you need moved.
__________________
Wind is your friend
Matt
|

March 27th, 2015, 08:12 AM
|
Friend of Wrox
|
|
Join Date: Jun 2003
Posts: 428
Thanks: 57
Thanked 2 Times in 2 Posts
|
|
That's what I thought.
Thanks!
|

March 27th, 2015, 10:33 AM
|
Authorized User
|
|
Join Date: Mar 2015
Posts: 34
Thanks: 3
Thanked 2 Times in 2 Posts
|
|
Still looking for solution?
|

March 27th, 2015, 10:39 AM
|
Friend of Wrox
|
|
Join Date: Jun 2003
Posts: 428
Thanks: 57
Thanked 2 Times in 2 Posts
|
|
What do you suggest?
|

March 28th, 2015, 03:30 PM
|
Friend of Wrox
|
|
Join Date: Jul 2003
Posts: 599
Thanks: 6
Thanked 3 Times in 3 Posts
|
|
I believe you can also detach the database and attach it in a different location.
Why can't you make a backup of the database?
|

March 29th, 2015, 06:46 PM
|
Friend of Wrox
|
|
Join Date: Jan 2004
Posts: 1,870
Thanks: 12
Thanked 20 Times in 20 Posts
|
|
IMO detach and attach is no where near as good as taking a backup. Also i doubt your ability to detach a database given your limited permissions. Base don your post I assume permissions is why you cant create a backup...
__________________
Wind is your friend
Matt
|

March 30th, 2015, 01:12 AM
|
Friend of Wrox
|
|
Join Date: Jul 2003
Posts: 599
Thanks: 6
Thanked 3 Times in 3 Posts
|
|
It works though, doesn't it? I haven't seen any difference myself.
If you don't have permission to back up the database maybe you should leave it alone.
|
|
 |