Adding TFS to the equation iwill increase the cost!

Cost is the usual reason given for not using VS database projects.

For me SSDT is one of the great things in 2012.. looking forward to the release next year 🙂

One thing the article does not take into account is all the backups that will be in-accessible if the certificates are removed. I have a couple of posts about this...

SMO is not consistent when raising exceptions for login failures.

I've blogged about Powershell error handling:

http://sqlblogcasts.com/blogs/martinbell/archive/2011/01/16/Powershell-Error-Handling.aspx

and raised this error on connect:

http://sqlblogcasts.com/blogs/martinbell/archive/2011/01/17/SMO-doesn_2700_t-always-raise-an-error-when-handling-login-failures.aspx

This may work for you, but it is not going to work or be a option for everyone.

Doug Bishop (11/29/2010)

---

I am still confused as to how using scripts is better than using stored procedures and using a job with multiple steps to control the flow. Furthermore, in...

Doug Bishop (11/29/2010)Okay, I am confused; license cost for what? A stored procedure is a script that has been saved to the database using CREATE PROCEDURE procname. There are no...

Doug Bishop (11/29/2010)

---

Why, oh why, oh why, oh why do people still insist on using scripts? They do it here too and it is frustrating.

Anyone ever hear about a...

For Oracle you can use SQL*Plus on a command line and the START option i.e. @filename will allow you to run a file. Alternatively you can use the START command...

Maybe my blog posts explains all of this better, it pre-dates all of these articles.

http://sqlblogcasts.com/blogs/martinbell/archive/2009/06/02/How-to-execute-multiple-sql-scripts.aspx

or if you use Powershell

http://sqlblogcasts.com/blogs/martinbell/archive/2009/07/30/Executing-all-.SQL-files-in-a-directory-with-Powershell.aspx

Martin

Sqlfrenzy (8/11/2009)

---

actually I was trying to communicate that if there is a begin tran without any corresponding rollback or

commit in the script to be executed...how this can be taken care...

This file can also be created from a batch file without manual intervention e.g.

del runsql.sql

echo :on error exit > runsql.lsq

for %%f in (*.sql) do ( echo :r "%%~ff" >> runsql.lsq...

I was talking...

I like this option :-), although you don't actually need to tokenise the output of the bare format...