Deploying new schema

[markphsd]

Where's some good documentation on deploying a new schema. I"m looking for a cost effective way to do it, using something like msdemanager or SQL Server.
thanks.

Mark P.

http://www.cafecartel.com

Providing Low Cost Powerful Point of Sale Solutions.

 

[mrdenny]

Deploying a new schema.

CREATE SCHEMA [i]SchemaName[/i]
go

I think that you need to provide some more information on what you are trying to do.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[markphsd]

Okay,

I expected more questions.

This is more for updating existing databases that will need the updated schema.

Mark P.

http://www.cafecartel.com

Providing Low Cost Powerful Point of Sale Solutions.

 

[mrdenny]

Changes to object schemas should be handled by the developers as they make the changes so that the updates can be rolled into qa and then production along with the procedures which use the new columns.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[markphsd]

I'm looking for an automated or semi automated process.

Well first off, developers won't be making changes to hundreds or thousands of databases. That would be impractical and problamatic

An update system has been in place for our Access deployments for several years now. However since we have switched over to SQL Server, we'll need an automated process for that as well.

What is the common way to deploy updates to a database used by many different customers? Is there a good tool that is used? That would probably be the best solution.


Mark P.

http://www.cafecartel.com

Providing Low Cost Powerful Point of Sale Solutions.

 

[mrdenny]

The common method is to include the ALTER TABLE scripts in what ever install process is given to the customer to upgrade the system.

In SQL Server all schema changes can be scripted out and run as simple T/SQL commands.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[markphsd]

Denny,

That's what I have read, and tried, and it's really easy. However, I had heard that it didn't always work. So i was looking for other alternatives.

Or, if there were some basic reasons for it failing, once this stuff get's deployed it's A pain when ten people call saying they have a problem each with different reasons.

Plus if there is a good tool, it'll give me the reporting of errors and answers i'm looking for..I hope.

I'll go with the scripts for a bit and see what happens.

Mark P.

http://www.cafecartel.com

Providing Low Cost Powerful Point of Sale Solutions.

 

[mrdenny]

Changing tables via scripts works 100% of the time...

Provided that no one is using the table when the change is being made. If there is someone using the table then the script will wait for the user to finish with the table (via standard database locking/blocking).

Anything that makes schema changes to a table uses the same methods under the covers and has the same restrictions to follow.

Because of this most people don't find any value in third party tools especially for stuff like this.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com