Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
TimSinnott
Starting Member
48 Posts |
 Posted - 2006-02-15 : 22:44:20
|
| I'm beginning to have a twinge of regret about my recent upgrading of my development machine from SQL Server 2000 to SQL Server 2005.I'm trying to deploy a small SQL Server 2005 database from my development machine to a new, empty SQL Server 2005 database at WebHost4Life. My database has a few small tables and a couple of stored procedures.In the good old days of SQL Server 2000, I could chose Tasks - Export/Import, then use the DTS wizard to choose which tables, stored procedures, etc., and other objects, I want to copy.But now, with SQL Server 2005, Export/Import only lets me choose tables. No sprocs, or anything.So, I tried another route, using SQL Server 2005's Copy Database wizard. The problem there is that one needs admin rights on the destination machine for that, and none of these web hosting companies dare give a customer such rights.So, I'm stumped. Does anybody know of a straightforward solution to this? I'm beginning to wonder why I was so eager to leave good old SQL Server 2000.Thanks in advance.TimSinnott |
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2006-02-15 : 23:12:02
|
| I saw somewhere recently about a bug in the copy process that didn't copy identity columns as well.Easiest way to fix it would be to ftp up a database backup and log a job with them to restore it for you.Damian"A foolish consistency is the hobgoblin of little minds." - Emerson |
 |
|
|
TimSinnott
Starting Member
48 Posts |
Posted - 2006-02-16 : 09:52:29
|
| Damian, that didn't occur to me. But I guess sooner or later I need to become comfortable with moving backup files around anyway (which I've not done much of), so your FTP method would have that additional advantage.Thanks.TimSinnott |
|
|
|
TimSinnott
Starting Member
48 Posts |
Posted - 2006-02-16 : 10:25:35
|
| It just occurred to me that with good old SQL 2000, for a changed stored procedure or something, I could easily use Export/Import to upload just that one new stored procedure from my development machine to my web hosting account. But I can't do that with SQL Server 2005, even with with backup/restore. I can only restore the whole darn database.So, that makes me think I'm probably better off going back to SQL Server 2000, until Microsoft gets SQL 2005 a little more complete.Any thoughts, anybody?TimSinnott |
|
|
|
|
|
|
|
|
SQL Server 2005 - copying data and objects