Re: create database: programmatically vs app-tools

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: R Reyes (RReyes_at_discussions.microsoft.com)
Date: 11/11/04 

Date: Thu, 11 Nov 2004 11:08:01 -0800

Thanks for the replies.

>From now on I think I will be creating all my databases with reusable
scripts.

Sounds like its definitely worth it.

"Ben Bloom" wrote:

> It's easier to migrate changes through development -> Test -> Production
> servers if the database is created in script. Just apply the script to
> a different server/database and you're set.
>
> If you use the GUI tools (which, I admit, are nice and easy) you have to
> manually change each database.
>
> Mark wrote:
>
> > Once you've typed the syntax once ... you can save it in a .sql or text file
> > and reuse it over and over and over. Once it's written, no more clicking -
> > just modify for the new database, and then execute. Moreover, there are a
> > myriad of configuration issues that affect performance, security, etc., that
> > sometimes are easy to overlook in the GUI, and would have to be addressed by
> > reading through BOL to write the syntax yourself. Consider it a "healthy"
> > excercise that will treat you well over the long haul.
> >
> > Good luck.
> >
> > Mark
> > www.dovetaildatabases.com
> >
> > "R Reyes" <RReyes@discussions.microsoft.com> wrote in message
> > news:895E9ABF-AB93-4FEC-9AE3-97A713D5A953@microsoft.com...
> >
> >>Just wondering if anyone knows the pros/cons between creating a database
> >>programmatically vs using the application's tool windows/features that
> >
> > come
> >
> >>with SQLServer, Access, Oracle, etc...
> >>
> >>Is it the same? Does it really matter? I have created databases with
> >
> > .NET
> >
> >>programmatically and it works fine, but why would anyone want to do all
> >
> > this
> >
> >>typing when they can easily point and click inside the program?
> >>
> >>It took a few hours of typing for me to create the database and all its
> >>tables. I am very certain that if i just point and clicked inside the
> >>program it would've been done in less than an hour. So why do people
> >>programmatically use SQL? Is it only on an as-needed basis or do many
> >
> > people
> >
> >>ALWAYS use this practice because it makes it more efficient/declarative?
> >
> >
> >
>
>
> --
> to reply, remove .s.p.a.m. from email
>

Relevant Pages

  • Re: Help with installing script
    ... Freebird wrote: ... > I've done a script that will work in many different servers, and now, I ... Do you want scripts to produce a database for Postgresql only? ...
    (comp.lang.php)
  • RE: Tool for creating upgrade scripts
    ... I'm with Mark on this one. ... it as an end to end SQL Server Database Change Management system. ... > promise but don't deliver) procucing a delta script to use on all your ... This is causing us some real problems as lots of settings and stored ...
    (microsoft.public.sqlserver.tools)
  • Re: fork,exec, and parallel processing
    ... I've a need for a script that can query multiple NetBackup servers for ... What can I do to correct the script so it ... my @clients; ... Dump the data you need into a Database then parse the database once ...
    (comp.lang.perl.misc)
  • Identifying IO bottlenecks
    ... I created a 30MB database on one of my servers, ... On server 1 this script takes 7 minutes to run - which seems ... On server 2, I ran the exact same script, however this time the script ...
    (microsoft.public.sqlserver.programming)
  • Re: Error 208: Invalid object name sysextendedarticlesview
    ... Then run this script. ... Looking for a book on SQL Server replication? ... > for maintainance tasks (converting database from SQL_Latin to Latin_General)> we scripted a working merge replication and removed it with Enterprise ... > This view indeed cannot be found on one of the participating servers, but on> a different set of servers, where the same kind of replication is still> running, this view can't be found either. ...
    (microsoft.public.sqlserver.replication)