Help with SQL 2005 solutions

Hi,
I want to be able to use source control from within SQL 2005. I know
how to add a new solution with a project attached. And I know how to
add existing .sql scripts to it. My quesiton is, how can I split them
up so that I can add all stored procedure scripts into a folder called
Stored Procedures, all views into a folder called Views etc instead of
them all going into the Query folder.
Appreciate any help on this.nomad
If I understood you correctly
1) Open Solution within you have added .sql files (1-for SP,2-for Views)
2) When you click on the file it opens a object explorer windows
3) Add your object to opened window (relevant for object type) and save it.
So , the next time you open the file your script should be saved there
"nomad" <d.bedgood@.ntlworld.com> wrote in message
news:1172065721.265467.175850@.a75g2000cwd.googlegroups.com...
> Hi,
> I want to be able to use source control from within SQL 2005. I know
> how to add a new solution with a project attached. And I know how to
> add existing .sql scripts to it. My quesiton is, how can I split them
> up so that I can add all stored procedure scripts into a folder called
> Stored Procedures, all views into a folder called Views etc instead of
> them all going into the Query folder.
> Appreciate any help on this.
>|||On 21 Feb, 14:16, "Uri Dimant" <u...@.iscar.co.il> wrote:
> nomad
> If I understood you correctly
> 1) Open Solution within you have added .sql files (1-for SP,2-for Views)
> 2) When you click on the file it opens a object explorer windows
> 3) Add your object to opened window (relevant for object type) and save it.
> So , the next time you open the file your script should be saved there
> "nomad" <d.bedg...@.ntlworld.com> wrote in message
> news:1172065721.265467.175850@.a75g2000cwd.googlegroups.com...
> > Hi,
> > I want to be able to use source control from within SQL 2005. I know
> > how to add a new solution with a project attached. And I know how to
> > add existing .sql scripts to it. My quesiton is, how can I split them
> > up so that I can add all stored procedure scripts into a folder called
> > Stored Procedures, all views into a folder called Views etc instead of
> > them all going into the Query folder.
> > Appreciate any help on this.
I know how to do all of this. My question is, in the solution you
have folders called Connections, Queries & Miscellaneous. I want to
be able to add folders called Stored Procedures, Views etc so that I
can add my SP .sql scripts into Stored Procedure folder, Views scripts
into Views folder etc so that it is easier to differentiate between
your scripts.|||Ahh, I see what you mean. I'm affraid you cannot do that
"nomad" <d.bedgood@.ntlworld.com> wrote in message
news:1172068385.736309.197940@.k78g2000cwa.googlegroups.com...
> On 21 Feb, 14:16, "Uri Dimant" <u...@.iscar.co.il> wrote:
>> nomad
>> If I understood you correctly
>> 1) Open Solution within you have added .sql files (1-for SP,2-for Views)
>> 2) When you click on the file it opens a object explorer windows
>> 3) Add your object to opened window (relevant for object type) and save
>> it.
>> So , the next time you open the file your script should be saved there
>> "nomad" <d.bedg...@.ntlworld.com> wrote in message
>> news:1172065721.265467.175850@.a75g2000cwd.googlegroups.com...
>> > Hi,
>> > I want to be able to use source control from within SQL 2005. I know
>> > how to add a new solution with a project attached. And I know how to
>> > add existing .sql scripts to it. My quesiton is, how can I split them
>> > up so that I can add all stored procedure scripts into a folder called
>> > Stored Procedures, all views into a folder called Views etc instead of
>> > them all going into the Query folder.
>> > Appreciate any help on this.
> I know how to do all of this. My question is, in the solution you
> have folders called Connections, Queries & Miscellaneous. I want to
> be able to add folders called Stored Procedures, Views etc so that I
> can add my SP .sql scripts into Stored Procedure folder, Views scripts
> into Views folder etc so that it is easier to differentiate between
> your scripts.
>|||On 21 Feb, 14:43, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Ahh, I see what you mean. I'm affraid you cannot do that
> "nomad" <d.bedg...@.ntlworld.com> wrote in message
> news:1172068385.736309.197940@.k78g2000cwa.googlegroups.com...
> > On 21 Feb, 14:16, "Uri Dimant" <u...@.iscar.co.il> wrote:
> >> nomad
> >> If I understood you correctly
> >> 1) Open Solution within you have added .sql files (1-for SP,2-for Views)
> >> 2) When you click on the file it opens a object explorer windows
> >> 3) Add your object to opened window (relevant for object type) and save
> >> it.
> >> So , the next time you open the file your script should be saved there
> >> "nomad" <d.bedg...@.ntlworld.com> wrote in message
> >>news:1172065721.265467.175850@.a75g2000cwd.googlegroups.com...
> >> > Hi,
> >> > I want to be able to use source control from within SQL 2005. I know
> >> > how to add a new solution with a project attached. And I know how to
> >> > add existing .sql scripts to it. My quesiton is, how can I split them
> >> > up so that I can add all stored procedure scripts into a folder called
> >> > Stored Procedures, all views into a folder called Views etc instead of
> >> > them all going into the Query folder.
> >> > Appreciate any help on this.
> > I know how to do all of this. My question is, in the solution you
> > have folders called Connections, Queries & Miscellaneous. I want to
> > be able to add folders called Stored Procedures, Views etc so that I
> > can add my SP .sql scripts into Stored Procedure folder, Views scripts
> > into Views folder etc so that it is easier to differentiate between
> > your scripts.
Thanks for your reply. I have got around it by having seperate
project for Stored Procedures and seperate project for Views.
Another question, if you don't mind. Obviously I will have these
scripted stored procedures and views within my solution, but that
still won't stop anyone from opening up the actual stored procedure or
view and altering it, without going through source control. Is there
a way of locking the actual stored procedures and views down so they
can only be altered via the scripts in source control?
Appreciate your help.|||nomad
There you have an option to add your scripts to VSS to keep versions
Regarding who can access to stored procedures , you can deny to users view
or alter your stored procedures, but this is a matter of your company's
policy
"nomad" <d.bedgood@.ntlworld.com> wrote in message
news:1172069673.298471.272100@.j27g2000cwj.googlegroups.com...
> On 21 Feb, 14:43, "Uri Dimant" <u...@.iscar.co.il> wrote:
>> Ahh, I see what you mean. I'm affraid you cannot do that
>> "nomad" <d.bedg...@.ntlworld.com> wrote in message
>> news:1172068385.736309.197940@.k78g2000cwa.googlegroups.com...
>> > On 21 Feb, 14:16, "Uri Dimant" <u...@.iscar.co.il> wrote:
>> >> nomad
>> >> If I understood you correctly
>> >> 1) Open Solution within you have added .sql files (1-for SP,2-for
>> >> Views)
>> >> 2) When you click on the file it opens a object explorer windows
>> >> 3) Add your object to opened window (relevant for object type) and
>> >> save
>> >> it.
>> >> So , the next time you open the file your script should be saved there
>> >> "nomad" <d.bedg...@.ntlworld.com> wrote in message
>> >>news:1172065721.265467.175850@.a75g2000cwd.googlegroups.com...
>> >> > Hi,
>> >> > I want to be able to use source control from within SQL 2005. I
>> >> > know
>> >> > how to add a new solution with a project attached. And I know how
>> >> > to
>> >> > add existing .sql scripts to it. My quesiton is, how can I split
>> >> > them
>> >> > up so that I can add all stored procedure scripts into a folder
>> >> > called
>> >> > Stored Procedures, all views into a folder called Views etc instead
>> >> > of
>> >> > them all going into the Query folder.
>> >> > Appreciate any help on this.
>> > I know how to do all of this. My question is, in the solution you
>> > have folders called Connections, Queries & Miscellaneous. I want to
>> > be able to add folders called Stored Procedures, Views etc so that I
>> > can add my SP .sql scripts into Stored Procedure folder, Views scripts
>> > into Views folder etc so that it is easier to differentiate between
>> > your scripts.
> Thanks for your reply. I have got around it by having seperate
> project for Stored Procedures and seperate project for Views.
> Another question, if you don't mind. Obviously I will have these
> scripted stored procedures and views within my solution, but that
> still won't stop anyone from opening up the actual stored procedure or
> view and altering it, without going through source control. Is there
> a way of locking the actual stored procedures and views down so they
> can only be altered via the scripts in source control?
> Appreciate your help.
>|||Take a look at visual studio team edition for database professionals.
I think it's the answer to your problem.
More information at http://msdn2.microsoft.com/en-us/teamsystem/aa718807.aspx
regards
"nomad" wrote:
> On 21 Feb, 14:43, "Uri Dimant" <u...@.iscar.co.il> wrote:
> > Ahh, I see what you mean. I'm affraid you cannot do that
> >
> > "nomad" <d.bedg...@.ntlworld.com> wrote in message
> >
> > news:1172068385.736309.197940@.k78g2000cwa.googlegroups.com...
> >
> > > On 21 Feb, 14:16, "Uri Dimant" <u...@.iscar.co.il> wrote:
> > >> nomad
> > >> If I understood you correctly
> > >> 1) Open Solution within you have added .sql files (1-for SP,2-for Views)
> > >> 2) When you click on the file it opens a object explorer windows
> > >> 3) Add your object to opened window (relevant for object type) and save
> > >> it.
> > >> So , the next time you open the file your script should be saved there
> >
> > >> "nomad" <d.bedg...@.ntlworld.com> wrote in message
> >
> > >>news:1172065721.265467.175850@.a75g2000cwd.googlegroups.com...
> >
> > >> > Hi,
> >
> > >> > I want to be able to use source control from within SQL 2005. I know
> > >> > how to add a new solution with a project attached. And I know how to
> > >> > add existing .sql scripts to it. My quesiton is, how can I split them
> > >> > up so that I can add all stored procedure scripts into a folder called
> > >> > Stored Procedures, all views into a folder called Views etc instead of
> > >> > them all going into the Query folder.
> >
> > >> > Appreciate any help on this.
> >
> > > I know how to do all of this. My question is, in the solution you
> > > have folders called Connections, Queries & Miscellaneous. I want to
> > > be able to add folders called Stored Procedures, Views etc so that I
> > > can add my SP .sql scripts into Stored Procedure folder, Views scripts
> > > into Views folder etc so that it is easier to differentiate between
> > > your scripts.
> Thanks for your reply. I have got around it by having seperate
> project for Stored Procedures and seperate project for Views.
> Another question, if you don't mind. Obviously I will have these
> scripted stored procedures and views within my solution, but that
> still won't stop anyone from opening up the actual stored procedure or
> view and altering it, without going through source control. Is there
> a way of locking the actual stored procedures and views down so they
> can only be altered via the scripts in source control?
> Appreciate your help.
>|||On Feb 21, 3:31 pm, Zekske <Zek...@.discussions.microsoft.com> wrote:
> Take a look at visual studio team edition for database professionals.
> I think it's the answer to your problem.
> More information athttp://msdn2.microsoft.com/en-us/teamsystem/aa718807.aspx
> regards
> "nomad" wrote:
> > On 21 Feb, 14:43, "Uri Dimant" <u...@.iscar.co.il> wrote:
> > > Ahh, I see what you mean. I'm affraid you cannot do that
> > > "nomad" <d.bedg...@.ntlworld.com> wrote in message
> > >news:1172068385.736309.197940@.k78g2000cwa.googlegroups.com...
> > > > On 21 Feb, 14:16, "Uri Dimant" <u...@.iscar.co.il> wrote:
> > > >> nomad
> > > >> If I understood you correctly
> > > >> 1) Open Solution within you have added .sql files (1-for SP,2-for Views)
> > > >> 2) When you click on the file it opens a object explorer windows
> > > >> 3) Add your object to opened window (relevant for object type) and save
> > > >> it.
> > > >> So , the next time you open the file your script should be saved there
> > > >> "nomad" <d.bedg...@.ntlworld.com> wrote in message
> > > >>news:1172065721.265467.175850@.a75g2000cwd.googlegroups.com...
> > > >> > Hi,
> > > >> > I want to be able to use source control from within SQL 2005. I know
> > > >> > how to add a new solution with a project attached. And I know how to
> > > >> > add existing .sql scripts to it. My quesiton is, how can I split them
> > > >> > up so that I can add all stored procedure scripts into a folder called
> > > >> > Stored Procedures, all views into a folder called Views etc instead of
> > > >> > them all going into the Query folder.
> > > >> > Appreciate any help on this.
> > > > I know how to do all of this. My question is, in the solution you
> > > > have folders called Connections, Queries & Miscellaneous. I want to
> > > > be able to add folders called Stored Procedures, Views etc so that I
> > > > can add my SP .sql scripts into Stored Procedure folder, Views scripts
> > > > into Views folder etc so that it is easier to differentiate between
> > > > your scripts.
> > Thanks for your reply. I have got around it by having seperate
> > project for Stored Procedures and seperate project for Views.
> > Another question, if you don't mind. Obviously I will have these
> > scripted stored procedures and views within my solution, but that
> > still won't stop anyone from opening up the actual stored procedure or
> > view and altering it, without going through source control. Is there
> > a way of locking the actual stored procedures and views down so they
> > can only be altered via the scripts in source control?
> > Appreciate your help.
Uri, How would you restrict view access but still allow the users to
alter?
Thanks for your time
Dmaon|||> Uri, How would you restrict view access but still allow the users to
> alter?
So , you say , they won't see what they altered/cretaed? :-))
"nomad" <d.bedgood@.ntlworld.com> wrote in message
news:1172152747.129528.282960@.j27g2000cwj.googlegroups.com...
> On Feb 21, 3:31 pm, Zekske <Zek...@.discussions.microsoft.com> wrote:
>> Take a look at visual studio team edition for database professionals.
>> I think it's the answer to your problem.
>> More information
>> athttp://msdn2.microsoft.com/en-us/teamsystem/aa718807.aspx
>> regards
>> "nomad" wrote:
>> > On 21 Feb, 14:43, "Uri Dimant" <u...@.iscar.co.il> wrote:
>> > > Ahh, I see what you mean. I'm affraid you cannot do that
>> > > "nomad" <d.bedg...@.ntlworld.com> wrote in message
>> > >news:1172068385.736309.197940@.k78g2000cwa.googlegroups.com...
>> > > > On 21 Feb, 14:16, "Uri Dimant" <u...@.iscar.co.il> wrote:
>> > > >> nomad
>> > > >> If I understood you correctly
>> > > >> 1) Open Solution within you have added .sql files (1-for SP,2-for
>> > > >> Views)
>> > > >> 2) When you click on the file it opens a object explorer windows
>> > > >> 3) Add your object to opened window (relevant for object type)
>> > > >> and save
>> > > >> it.
>> > > >> So , the next time you open the file your script should be saved
>> > > >> there
>> > > >> "nomad" <d.bedg...@.ntlworld.com> wrote in message
>> > > >>news:1172065721.265467.175850@.a75g2000cwd.googlegroups.com...
>> > > >> > Hi,
>> > > >> > I want to be able to use source control from within SQL 2005. I
>> > > >> > know
>> > > >> > how to add a new solution with a project attached. And I know
>> > > >> > how to
>> > > >> > add existing .sql scripts to it. My quesiton is, how can I
>> > > >> > split them
>> > > >> > up so that I can add all stored procedure scripts into a folder
>> > > >> > called
>> > > >> > Stored Procedures, all views into a folder called Views etc
>> > > >> > instead of
>> > > >> > them all going into the Query folder.
>> > > >> > Appreciate any help on this.
>> > > > I know how to do all of this. My question is, in the solution you
>> > > > have folders called Connections, Queries & Miscellaneous. I want
>> > > > to
>> > > > be able to add folders called Stored Procedures, Views etc so that
>> > > > I
>> > > > can add my SP .sql scripts into Stored Procedure folder, Views
>> > > > scripts
>> > > > into Views folder etc so that it is easier to differentiate between
>> > > > your scripts.
>> > Thanks for your reply. I have got around it by having seperate
>> > project for Stored Procedures and seperate project for Views.
>> > Another question, if you don't mind. Obviously I will have these
>> > scripted stored procedures and views within my solution, but that
>> > still won't stop anyone from opening up the actual stored procedure or
>> > view and altering it, without going through source control. Is there
>> > a way of locking the actual stored procedures and views down so they
>> > can only be altered via the scripts in source control?
>> > Appreciate your help.
> Uri, How would you restrict view access but still allow the users to
> alter?
> Thanks for your time
> Dmaon
>