need help : SQL Server and Clear Case

Environment

1)We are using VBA,MS Access 2000/2003 and SQL Server 2000 in our
project.

2)We need to use Rational clear case as the SCM tool.

Our Work

Our work primarily falls in developing SQL Server stored procedures,
functions and few  VisualBasicForAccess
(VBA) code.


Technical Help sought

1) Does SQL Server 2000 provide any inbuilt capabilities of Software
Configuration Management(SCM)?Not that I am aware of other than
extending it with other DM management tools like BMC,A&G,VERITAS etc.

2)If not, Is there any plug-in available in SQL Server environment that
can be installed on SQL Server so that any code developed [Stored
procedures/functions etc] can be managed in Clearcase.[I am looking for
Eclipse plugin's kind of plugins which would enable you to check in and
check out from Eclipse after the initial configuration is done on
Eclipse]?

3)If plugins are not available then the option we have is, manual and
external check in and check out the code bits in to Clearcase.Can some
one point me to concise and relevant user manual on this.

The MSSQL 2000 client tools have no direct SCM integration (the 2005
ones do), although QA allows you to run batch files with parameters
such as the currently open file, so you could develop some basic
scripts yourself. Visual Studio might be an option if you're already
using it, but personally I just check out a file (from VSS) and start
editing it in QA. I have no idea how ClearCase works, so I can't really
comment on that tool specifically.

Simon

(db2sysc@gmail.com)  writes:
> 2)If not, Is there any plug-in available in SQL Server environment that
> can be installed on SQL Server so that any code developed [Stored
> procedures/functions etc] can be managed in Clearcase.[I am looking fo
r
> Eclipse plugin's kind of plugins which would enable you to check in and
> check out from Eclipse after the initial configuration is done on
> Eclipse]?

I have no experience of ClearCase, but stored procedures etc are no
different from everything else you have under source control. It's
just files. Some people think they are database objects, but that
is the "binary" representation, so to speak.

Sure, some people think it's nice to check out a file from the
version-control system directly in the tool. I for my part, prefer
to access the CM tool directly (in my case SourceSafe), so I know what
is going on.



--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp