Re: Sql Server Login
From: nntp.broadband.rogers.com (hemang_at_hemang.net)
Date: 01/09/05
- Next message: quilkin: "Finding user(s) currently logged in"
- Previous message: Anthony Carrabino: "VistaDB 2.0.12 released with many improvements"
- In reply to: Andrea Montanari: "Re: Sql Server Login"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 9 Jan 2005 08:37:17 -0500
Thank you so much for your reply.
Ok, firstly I was under the impression SQL authenticaiton will be better
because how will the cient's computer have my userid for windows
authentication.
But now I know windows authentication is recommended. So I'll use that.
However I'm still confused as to how will the client be able to use it ?
Let me explain what I mean.
I install MDSE on my computer at work with "windows authentication" (as
default). I create a database on it and I'll have to select windows
authentication during that. I create tables, relations and develop my
application using c# to talk to it.
Migrate client's old data from access to this database.(any kb articles on
this?) Now my application is ready and talking to this database in MSDE.
Now the question is:
How do I give my client permission to this database when I don't know their
userid and have no access to their windows security model. I haven't gone
through the articles you pointed me to, but these questions poped up in my
mind and thought would ask you.
Another question I had while I was reading the readme of MSDE is that I can
install up to 16 instances of MSDE on a single computer.
If I can create multiple databases in MSDE, why would I need multiple
instances ? What is an instance and the advantages of having more than one
on the same computer.
Thanks for all the help.
Hemang
"Andrea Montanari" <andrea.sqlDMO@virgilio.it> wrote in message
news:<34011eF450qukU1@individual.net>...
> hi again,
> "Andrea Montanari" <andrea.sqlDMO@virgilio.it> ha scritto nel
> messaggio news:33vvkpF43u1qrU1@individual.net
> >>
> >> Which is better for creating the database on one computer and then
> >> deploying it at the customer site.
> >>
> >> Are there any documents which explain how to copy a database from
> >> development site to production site?
> >>
>
> as regard this last part, I personally am aware of 3 ways to do it..
> and ech of them has it's drawbacks...
> 1) you can detach your dev database, copy it on the user's machine,
> and reattach it .. using sp_detach_db to detach it and sp_attach_db
> for reattach, see BOL for further info....
> 2) you can backup your dev database and restore in on the user's
> machine...
> see backup database and restore database in BOL for further info....
>
> these 2 methods are quite easy to perform but suffer from some drawbacks..
> - they can raise orphan users issue (please see
> http://www.sqlservercentral.com/columnists/nboyle/fixingbrokenlogins.a
> sp for further info and details on how to solve this)
> - they do not make use of user's model database... every database
> inherits settings, dbobjects, sometimes permissions, from the current
> model database... if you deploy your database schema these way you
> simply export YOUR settings and preferences..
> - they inherits your settings regarding collation and sort order....
> this is no more a problem with SQL Server 200 becouse it supports
> different collations, but was a major issue for SQL Server 7.0
> deployment..
>
> 3) you can script out your DDL database schema with tools like
> Enterprise Manager or other (free) scripting tools...
> this method is the more elastic one, even if it require more deal...
> I currently deploy my dbs this way...
> I deploy sql DDL script to re-create the schema, sql permission
> scripts to generate privileges and users, sql DML "Insert Into" script
> to pre-load some application's system-tables and/or txt files to BCP in
> data...
> I do use a companion application which parses a private defintion
> files that includes settings as long as a list of files to be
> "executed" some way... I do use ADO and/or SQL-DMO, but oSql.exe can
> be an alternative, even if it does not set the OS error level status
> on Win9x boxes... I chose not to use oSql for this reason...
> even if more complicated, this method allows me to deploy database
> upgrades with no pain, providing the sql DDL script to morphe
> databases to current release.. several tools can help you for this
> please have a look at http://tinyurl.com/64jjy for a little more
> detailed explanation about the method...
>
> recently Microsoft released an excellent article base on scripting you
> can read at
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql
> mag01/html/scriptingacustomdatabaseinstallation.asp
> and this is by far the best article I ever read about..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1 (my vb6+sql-dmo little try to
> provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> --------- remove DMO to reply
>
"Andrea Montanari" <andrea.sqlDMO@virgilio.it> wrote in message
news:34011eF450qukU1@individual.net...
> hi again,
> "Andrea Montanari" <andrea.sqlDMO@virgilio.it> ha scritto nel messaggio
> news:33vvkpF43u1qrU1@individual.net
>>>
>>> Which is better for creating the database on one computer and then
>>> deploying it at the customer site.
>>>
>>> Are there any documents which explain how to copy a database from
>>> development site to production site?
>>>
>
> as regard this last part, I personally am aware of 3 ways to do it.. and
> ech
> of them has it's drawbacks...
> 1) you can detach your dev database, copy it on the user's machine, and
> reattach it .. using sp_detach_db to detach it and sp_attach_db for
> reattach, see BOL for further info....
> 2) you can backup your dev database and restore in on the user's
> machine...
> see backup database and restore database in BOL for further info....
>
> these 2 methods are quite easy to perform but suffer from some drawbacks..
> - they can raise orphan users issue (please see
> http://www.sqlservercentral.com/columnists/nboyle/fixingbrokenlogins.asp
> for
> further info and details on how to solve this)
> - they do not make use of user's model database... every database inherits
> settings, dbobjects, sometimes permissions, from the current model
> database... if you deploy your database schema these way you simply export
> YOUR settings and preferences..
> - they inherits your settings regarding collation and sort order.... this
> is
> no more a problem with SQL Server 200 becouse it supports different
> collations, but was a major issue for SQL Server 7.0 deployment..
>
> 3) you can script out your DDL database schema with tools like Enterprise
> Manager or other (free) scripting tools...
> this method is the more elastic one, even if it require more deal...
> I currently deploy my dbs this way...
> I deploy sql DDL script to re-create the schema, sql permission scripts to
> generate privileges and users, sql DML "Insert Into" script to pre-load
> some
> application's system-tables and/or txt files to BCP in data...
> I do use a companion application which parses a private defintion files
> that
> includes settings as long as a list of files to be "executed" some way...
> I
> do use ADO and/or SQL-DMO, but oSql.exe can be an alternative, even if it
> does not set the OS error level status on Win9x boxes... I chose not to
> use
> oSql for this reason...
> even if more complicated, this method allows me to deploy database
> upgrades
> with no pain, providing the sql DDL script to morphe databases to current
> release.. several tools can help you for this
> please have a look at http://tinyurl.com/64jjy for a little more detailed
> explanation about the method...
>
> recently Microsoft released an excellent article base on scripting you can
> read at
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlmag01/html/scriptingacustomdatabaseinstallation.asp
> and this is by far the best article I ever read about..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> --------- remove DMO to reply
>
- Next message: quilkin: "Finding user(s) currently logged in"
- Previous message: Anthony Carrabino: "VistaDB 2.0.12 released with many improvements"
- In reply to: Andrea Montanari: "Re: Sql Server Login"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
