Re: help :Deploying a preconfigured database
- From: "Keith Kratochvil" <sqlguy.back2u@xxxxxxxxxxx>
- Date: Thu, 30 Jun 2005 07:53:04 -0500
A couple of options are:
Backup and Restore
sp_detach_db and sp_attach_db
Another option:
You could create a script that would create a database, create the tables,
views, stored procedures, user defined functions for you. This would take
more prep work and testing because you want to make sure that everything is
scripted to happen in the proper order.
--
Keith
"serge calderara" <sergecalderara@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:27085A26-B8F6-465E-B0A5-7EB660D66AC0@xxxxxxxxxxxxxxxx
> Thnaks for your reply.
>
> What about the whole database structure and rights to table and strore
> procedure...
> How to deployed them in a safe and straight way on the target customer
> server and have at the end a traight forward running database copy of what
> has been tested on a test server environement ?
>
> Sorry for the basic question but I am new in SQL and that a customer
> request. never do that before so if you could help me that will be great
>
> Regards
> serge
>
> "Keith Kratochvil" wrote:
>
>> You can use the following KB article to script logins:
>>
>> HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
>> http://support.microsoft.com/default.aspx?scid=kb;EN-US;q246133
>>
>> You will want to make sure that you create appropriate script files to
>> set
>> up the logins and assign the permissions. You should be able to run
>> these
>> files via osql.exe (a command line tool). You will want to provide
>> whatever
>> error checking is necessary within the script so that you do not get
>> errors.
>> For example, lets say that your config requires the SQL Server login
>> 'user.'
>> You need to create user. If your script attempts to create user but they
>> already exist an error will be displayed and that could halt everything
>> that
>> comes after that specific point within the script. You will first want
>> to
>> check to see if user exists. If they do, do nothing. If not, add them.
>>
>> --
>> Keith
>>
>>
>> "serge calderara" <sergecalderara@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> message news:BC62E884-8286-44B9-B68C-D6E92148259F@xxxxxxxxxxxxxxxx
>> > Dear all,
>> >
>> > One of our application consist of configuring an SQL server database
>> > with
>> > user rights to tables and preparing corresponding store procedure.
>> >
>> > usually when we do this, we prepare the server in our test environment
>> > and
>> > then ship the whole hardware pre configure to customers.
>> >
>> > in some cases we do not have the customer server, so we need to do the
>> > whole
>> > configuration on site and in cas of errors its hard to find.
>> >
>> > is there an easy way to prepare the SQL confisuration database, store
>> > procedure, table rights on a test PC, then do a kind of straight
>> > forward
>> > deployement on any server running SQL ?
>> >
>> > thanks for your help
>> > regards
>> > Serge
>> >
>>
>>
>>
.
- References:
- help :Deploying a preconfigured database
- From: serge calderara
- Re: help :Deploying a preconfigured database
- From: Keith Kratochvil
- Re: help :Deploying a preconfigured database
- From: serge calderara
- help :Deploying a preconfigured database
- Prev by Date: Re: help :Deploying a preconfigured database
- Next by Date: Re: help :Deploying a preconfigured database
- Previous by thread: Re: help :Deploying a preconfigured database
- Next by thread: Re: help :Deploying a preconfigured database
- Index(es):
Relevant Pages
|