Nov 10, 2006 05:58 AM|shados|LINK
Thats where things get less fun... its an ongoing issue with SQL Server from my experience, but a necessary evil: SQL Server is incredibly picky when it comes to moving databases, because it rather not work at all, than working but leaving you with a broken
database (I mean, SQL Server -is- used to run banks and stuff!).
I had issues like that even on servers that I had built and installed from scratch myself, and had admin access on. There's always a solution, but while I've been a DBA, I'm not a guru.
That being said, if you go back to my walkthrough, at some point I have a reference to when you check a box to "script all objects". Uncheck that, and hit next. You will be presented with a ton of options to include/exclude stuff. You know what your database
contains, you know what you want, so only leave that (I'm guessing the tables...the constraints and indexes/keys, thats about it?), and remove everything else, then go on and follow the instructions on screen. It should be relatively comprehensive. By removing
as much as possible from what the engine scripts, you remove potential permission issues.