SQL script file and executing it

[Jason]

Hi

I would like to create a .NET app that can receive an SQL script file as
input. it will take the script file and execute it on the database,
depending on what connection properties were entered by the user. best way?

Thanks
Jason

[Michael Bray]

"Jason" <c_*******@mighty.co.za> wrote in
news:u1*************@TK2MSFTNGP11.phx.gbl:

Hi

I would like to create a .NET app that can receive an SQL script file
as input. it will take the script file and execute it on the database,
depending on what connection properties were entered by the user. best
way?

Perhaps just read the text in and use SqlConnection.ExecuteNonQuery(). I
believe (not 100% on this) that it will handle multiple commands just fine
- no need to try to parse it out into separate commands.

-mdb

[Jason]

yeh, my initial thought was that. just thought maybe there was another way
that would be better?

"Michael Bray" <mb*******************@SkPiAlMl.ctiusa.com> wrote in message
news:Xn**********************************@207.46.2 48.16...

"Jason" <c_*******@mighty.co.za> wrote in
news:u1*************@TK2MSFTNGP11.phx.gbl:

Hi

I would like to create a .NET app that can receive an SQL script file
as input. it will take the script file and execute it on the database,
depending on what connection properties were entered by the user. best
way?

Perhaps just read the text in and use SqlConnection.ExecuteNonQuery(). I
believe (not 100% on this) that it will handle multiple commands just fine
- no need to try to parse it out into separate commands.

-mdb

[Jason]

ah hmmm

thanks Rasika. yeh i wanna do this :-) because this is for installation
purposes. it is done by the installation program and not by users, if thats
what you mean by your last point?

is there another easier way of deploying databases?

Thanks
Jason

"Rasika" <ra**********@luckymail.com> wrote in message
news:A6**********************************@microsof t.com...

you can pass the sql string to a stored proc in MSSQL and use the exec function to execute it. But do you really want to do that. People can drop
tables and play all srot of havoc with your DB?
Rasika

[Branimir Giurov]

Check this one out:
--
Branimir Giurov
MCSD.NET, MCDBA, MCT
eAgility LLC
"Jason" <c_*******@mighty.co.za> wrote in message
news:O2*************@TK2MSFTNGP10.phx.gbl...

ah hmmm

thanks Rasika. yeh i wanna do this :-) because this is for installation
purposes. it is done by the installation program and not by users, if thats what you mean by your last point?

is there another easier way of deploying databases?

Thanks
Jason

"Rasika" <ra**********@luckymail.com> wrote in message
news:A6**********************************@microsof t.com...

you can pass the sql string to a stored proc in MSSQL and use the exec

function to execute it. But do you really want to do that. People can drop
tables and play all srot of havoc with your DB?

Rasika

[Branimir Giurov]

Check this one out:

http://msdn.microsoft.com/library/de...l/msdedepl.asp

Cheers,
Branimir

--
Branimir Giurov
MCSD.NET, MCDBA, MCT
eAgility LLC

"Jason" <c_*******@mighty.co.za> wrote in message
news:O2*************@TK2MSFTNGP10.phx.gbl...

ah hmmm

thanks Rasika. yeh i wanna do this :-) because this is for installation
purposes. it is done by the installation program and not by users, if thats what you mean by your last point?

is there another easier way of deploying databases?

Thanks
Jason

"Rasika" <ra**********@luckymail.com> wrote in message
news:A6**********************************@microsof t.com...

you can pass the sql string to a stored proc in MSSQL and use the exec

function to execute it. But do you really want to do that. People can drop
tables and play all srot of havoc with your DB?

Rasika