<div>
No need to do anything special.<br><br>We just make a folder named SQL Script or DB Scripts and whenever we change an SP or a View we copy over definition. This cannot get any simpler than that.
</div>


No need to do anything special.

We just make a folder named SQL Script or DB Scripts and whenever we change an SP or a View we copy over definition. This cannot get any simpler than that.

<div>
Thanks Chinmay, <br>But, how you get the version history? <br><br>
</div>


Thanks Chinmay,
But, how you get the version history?



<div>
Basically you have to maintain them yourself. For example, Dev1 made a change to the SP, S/he must check it in. Next time Dev2 made a change then the changes must be checked in, similar to any file that you put in GIT, version history will be maintained by GIT just like any other file.
</div>


Basically you have to maintain them yourself. For example, Dev1 made a change to the SP, S/he must check it in. Next time Dev2 made a change then the changes must be checked in, similar to any file that you put in GIT, version history will be maintained by GIT just like any other file.

<div>
The requirement Chinmay , is to get all SP's and views in the GIT.&nbsp;
</div>


The requirement Chinmay , is to get all SP's and views in the GIT. 

RIAS

<div>
But, for that I need to get all SP from SSMS &nbsp;to a folder isn't it? &nbsp;
</div>


But, for that I need to get all SP from SSMS  to a folder isn't it?  

<div>
Thanks Chinmay, our comments were having a bit of lag in posting.&nbsp;
</div>


Thanks Chinmay, our comments were having a bit of lag in posting. 

<div>
Just out of curiosity, is there a way to connect SSMS to git&nbsp; local repository) ?&nbsp;
</div>


Just out of curiosity, is there a way to connect SSMS to git  local repository) ? 

<div>
<blockquote>But, for that I need to get all SP from SSMS &nbsp;to a folder isn't it? &nbsp;</blockquote>Yes. SSMS can do that for you easily. You may use SSDT from within Visual Studio as well.
</div>


> But, for that I need to get all SP from SSMS  to a folder isn't it?  

Yes. SSMS can do that for you easily. You may use SSDT from within Visual Studio as well.

<div>
You may use SSDT from within Visual Studio as well. : <br>Exactly, that's exactly I was trying to do now.&nbsp;
</div>


You may use SSDT from within Visual Studio as well. :
Exactly, that's exactly I was trying to do now. 

<div>
No but you have SSDT which is inside VS. You don't really needs SSMS... Please have a look in Visual Studio after installing SSDT (I will be surprised if it is not installed already):<br>View -&gt; SQL Server Object Explorer -&gt; SQL Server -&gt; TargetDB -&gt; Tables -&gt; Right Click -&gt; Script As..<br>Similarly you can use&nbsp;<br>Programmability -&gt; Stored Procedures for SP<br>Views -&gt; for View<br><br>
</div>


No but you have SSDT which is inside VS. You don't really needs SSMS... Please have a look in Visual Studio after installing SSDT (I will be surprised if it is not installed already):
View -> SQL Server Object Explorer -> SQL Server -> TargetDB -> Tables -> Right Click -> Script As..
Similarly you can use 
Programmability -> Stored Procedures for SP
Views -> for View



<div>
Ok, just checking that. Thanks a ton.
</div>


<div>
Refer to my earlier comment:<blockquote>View -&gt; SQL Server Object Explorer -&gt; SQL Server -&gt; TargetDB -&gt; Tables -&gt; Right Click -&gt; Script As..</blockquote><br>
</div>


Refer to my earlier comment:

> View -> SQL Server Object Explorer -> SQL Server -> TargetDB -> Tables -> Right Click -> Script As..


<div>
&nbsp;TargetDB -&gt; Tables -&gt; Right Click -&gt; Script As.<br>No not that option, I need to add the SQL server tools in VS 2019. Thanks a ton. Will not disturb you.&nbsp;
</div>


 TargetDB -> Tables -> Right Click -> Script As.
No not that option, I need to add the SQL server tools in VS 2019. Thanks a ton. Will not disturb you. 

<div>
All sorted Chinmay, thanks!
</div>


<div>
SSDT is already installed. Good to hear that everything is sorted.
</div>


SSDT is already installed. Good to hear that everything is sorted.

<div>
it was not installed, had to modify the setup and check that option in other tools. Thanks
</div>


it was not installed, had to modify the setup and check that option in other tools. Thanks

<div>
Interesting. I thought if you have SQL Server Object Explorer you should have everything. Thanks for this one. I shall keep it in mind.
</div>


Interesting. I thought if you have SQL Server Object Explorer you should have everything. Thanks for this one. I shall keep it in mind.

<div>
<div class="content wysiwyg-content fr-view">
Hello Experts, <br>Is there anyway I can integrate git ( local repository ) with Stored Procedures and Views. <br><br>Thanks<br><br>
</div>
</div>



Hello Experts,
Is there anyway I can integrate git ( local repository ) with Stored Procedures and Views.
Thanks

Integrate GIT with SQL Server Stored Procedures and Views.

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.

Microsoft SQL Server

The .NET Framework is not specific to any one programming language; rather, it includes a library of functions that allows developers to rapidly build applications. Several supported languages include C#, VB.NET, C++ or ASP.NET.

.NET Programming

Git is a version control system for software development. It is a distributed revision control system with an emphasis on speed, data integrity, and support for distributed, non-linear workflows. Git was initially designed and developed for Linux kernel development. As with most other distributed version control systems, every Git working directory is a full-fledged repository with complete history and full version-tracking capabilities, independent of network access or a central server.

SQL (Structured Query Language) is designed to be used in conjunction with relational database products as of a means of working with sets of data. SQL consists of data definition, data manipulation, and procedural elements. Its scope includes data insert, query, update and delete, schema creation and modification, and data access control.