Mark Morgan Lloyd wrote:
Elsewhere, somebody was asking how people implemented version control
for stored procedures on (MS) SQL Server.
The consensus was that this is probably best managed by using scripts or
command files to generate stored procedures etc., but does anybody have
any comment
On Thu, Jun 30, 2016 at 09:16:49AM -0500, Merlin Moncure wrote:
> It's not really necessary to create version down scripts. In five
> years of managing complex database environments we've never had to
> roll a version back and likely never will; in the event of a disaster
> it's probably better t
On 07/01/2016 06:17 PM, Jim Nasby wrote:
On 6/30/16 9:16 AM, Merlin Moncure wrote:
It's not really necessary to create version down scripts. In five
years of managing complex database environments we've never had to
roll a version back and likely never will; in the event of a disaster
it's pr
On 6/30/16 9:16 AM, Merlin Moncure wrote:
It's not really necessary to create version down scripts. In five
years of managing complex database environments we've never had to
roll a version back and likely never will; in the event of a disaster
it's probably better to restore from backup anyways
On Wed, Jun 29, 2016 at 1:46 PM, Neil Anderson wrote:
> On 2016-06-29 12:37 PM, Mark Morgan Lloyd wrote:
>>
>> Elsewhere, somebody was asking how people implemented version control
>> for stored procedures on (MS) SQL Server.
>>
>> The consensus was that this is probably best managed by using scri
Mike Sofen wrote:
-Original Message-
From: Mark Morgan Lloyd Sent: Thursday, June 30, 2016 2:41 AM
Neil Anderson wrote:
On 2016-06-29 12:37 PM, Mark Morgan Lloyd wrote:
Elsewhere, somebody was asking how people implemented version control
for stored procedures on (MS) SQL Serve
-Original Message-
>From: Mark Morgan Lloyd Sent: Thursday, June 30, 2016 2:41 AM
>Neil Anderson wrote:
>> On 2016-06-29 12:37 PM, Mark Morgan Lloyd wrote:
>>> Elsewhere, somebody was asking how people implemented version control
>>> for stored procedures on (MS) SQL Server.
>>>
>>
Neil Anderson wrote:
On 2016-06-29 12:37 PM, Mark Morgan Lloyd wrote:
Elsewhere, somebody was asking how people implemented version control
for stored procedures on (MS) SQL Server.
The consensus was that this is probably best managed by using scripts or
command files to generate stored procedu
On 2016-06-29 12:37 PM, Mark Morgan Lloyd wrote:
Elsewhere, somebody was asking how people implemented version control
for stored procedures on (MS) SQL Server.
The consensus was that this is probably best managed by using scripts or
command files to generate stored procedures etc., but does any
On 2016-06-29 12:37 PM, Mark Morgan Lloyd wrote:
Elsewhere, somebody was asking how people implemented version control
for stored procedures on (MS) SQL Server.
The consensus was that this is probably best managed by using scripts or
command files to generate stored procedures etc., but does any
>does anybody have any comment on that from the POV of PostgreSQL?
Might be overkill but you could deploy your procedure as an extension
because extensions come with version control:
https://www.postgresql.org/docs/current/static/sql-createextension.html
Another option might be to hack something
On Wed, Jun 29, 2016 at 12:00 PM, Adrian Klaver
wrote:
> On 06/29/2016 09:37 AM, Mark Morgan Lloyd wrote:
>>
>> Elsewhere, somebody was asking how people implemented version control
>> for stored procedures on (MS) SQL Server.
>>
>> The consensus was that this is probably best managed by using scr
On 06/29/2016 09:37 AM, Mark Morgan Lloyd wrote:
Elsewhere, somebody was asking how people implemented version control
for stored procedures on (MS) SQL Server.
The consensus was that this is probably best managed by using scripts or
command files to generate stored procedures etc., but does any
13 matches
Mail list logo
