Re: Advice needed: Best way to deploy/manage SQL db website
- From: "sloan" <sloan@xxxxxxxxx>
- Date: Wed, 20 Feb 2008 21:13:46 -0500
If your hosting company ONLY does non-express databases, then I wouldn't
stick with Express.
Spend the $50 or so for developers editon of Sql Server 2005.
...
My advice. Code EVERYTHING in TSQL.
Create Table
Constraints
Baseline Data
Alter Table
Create Procedure
...
It makes a remote deployment much easier in my opinion.
The other things by going to "tsql only" mode is that you don't LOSE work
you do in the GUI.
Let's say you need to make a not null column...nullable.
Yeah, you can GUI go in and uncheck or check a box. But that work is "lost"
because if you ever need to repeat it....you need to re-GUI it.
Write a good ALTER TABLE script...and you have that (forever) to fall back
on.
That's my take. I have people at my own company who disagree with me..so
you know.........
But when it comes time to DEPLOY a real version of the database......I can
do it the fastest everytime.
..............
Here is another trick.
lets say you have some folders:
/Scripts/
/Scripts/usp/
/Scripts/udf/
/Scripts/ddl/
I put a .bat file in /Scripts/ to "merge" all my files.
/Scripts/usp/uspEmployeeGetByKey.sql
/Scripts/usp/uspEmployeeGetAll.sql
/Scripts/usp//uspEmployeeUpdate.sql
/Scripts/udf/udfEmployeeIsFullTime.sql
then in my .bat file...
/Scripts/tsql_merged.bat
and it contains
COPY ./usp/*.sql + ./udf/*.sql MERGED_TSQL.sql
that's a little trick....
The ddl is a little tricker, because it has to be in the correct order.
this "bat" tip....
that's a minor thing compared to the overall "use TSQL" tip above..but I
like it.
I keep every usp, every udf in a different file.
This helps maintenance and helps a group environment.
But even personal "just me" projects, I use the same format.
Good luck. Opinions might vary on this one.
"Bobby Edward" <test@xxxxxxxx> wrote in message
news:OxKPRCCdIHA.4476@xxxxxxxxxxxxxxxxxxxxxxx
Here's the situation....
1. Local dev environment is VS2005 and VS2008 / using SQL Express
databases for data
2. Hosting company ONLY supports MS SQL Server 2005 databases
Here are the questions...
1. Should I develop using SQL Express, or would my life be easier if I
had my local dev machine connected to a local SQL Server db? Any
advantages or disadvantages?
2. After I'm done developing the website I want to deploy it in such a
way that if I have to change the database schema (add fields, tables,
etc...) in the future it's easy to do. Any recommendations?
I guess I'm not quite sure as to what is the "proper" way to make db
changes to a db already in production (changes to schema, fields, tables,
etc...)? I'm kind of lost.
What is the best way to do this?
.
- References:
- Advice needed: Best way to deploy/manage SQL db website
- From: Bobby Edward
- Advice needed: Best way to deploy/manage SQL db website
- Prev by Date: RE: local time for remote users
- Next by Date: Re: String format
- Previous by thread: Advice needed: Best way to deploy/manage SQL db website
- Next by thread: Re: Advice needed: Best way to deploy/manage SQL db website
- Index(es):
Relevant Pages
|
