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
>
Showing posts with label project. Show all posts
Showing posts with label project. Show all posts
Wednesday, March 28, 2012
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:[vbcol=seagreen]
> 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 i
t.
> 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...
>
>
>
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:
> 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:[vbcol=seagreen]
> 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...
>
>
>
>
>
>
>
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:
> 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 [url]http://msdn2.microsoft.com/en-us/teamsystem/aa718807.aspx[/url
]
regards
"nomad" wrote:
> On 21 Feb, 14:43, "Uri Dimant" <u...@.iscar.co.il> wrote:
> 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:[vbcol=seagreen]
> 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.as
px
> regards
> "nomad" wrote:
>
>
>
>
>
>
>
>
>
>
>
>
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:
> Uri, How would you restrict view access but still allow the users to
> alter?
> Thanks for your time
> Dmaon
>sql
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:[vbcol=seagreen]
> 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 i
t.
> 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...
>
>
>
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:
> 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:[vbcol=seagreen]
> 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...
>
>
>
>
>
>
>
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:
> 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 [url]http://msdn2.microsoft.com/en-us/teamsystem/aa718807.aspx[/url
]
regards
"nomad" wrote:
> On 21 Feb, 14:43, "Uri Dimant" <u...@.iscar.co.il> wrote:
> 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:[vbcol=seagreen]
> 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.as
px
> regards
> "nomad" wrote:
>
>
>
>
>
>
>
>
>
>
>
>
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:
> Uri, How would you restrict view access but still allow the users to
> alter?
> Thanks for your time
> Dmaon
>sql
Monday, March 26, 2012
Help with SOAP Lite client error problems - CGI code
Hi,
I have been working on a soap client project for over a week now and can not figure out what I am doing wrong. I am not an expert using Perl or SOAP so any help would be "greatly" appreciated.
I get basic errors throughout, starting with:
Error - SOAP::Transport::HTTP::Client::send_receive: POST
It seems as if the user access information is not carried through as it should, but I truly have no idea what the problem is.
Here is what I have put together so far.
Thanks,
Mark
sub procgetmemberinfo {
my $pin = "$form{'lPin'}";
my $password = "$form{'sPassword'}";
my $soap = SOAP::Lite
-> uri('https://xmlsql.XXXXX.xxx:441')
-> on_action( sub { join '/', 'https://xmlsql.XXXXX.xxx:441', $_[1] } )
-> proxy('https://xmlsql.XXXXX.xxx:441/service.asmx?WSDL');
my @.params = (
SOAP::Data->name(lPin => $pin),
SOAP::Data->name(sPassword => $password)
);
my $method = SOAP::Data->name('GetMemberInfo')->attr({xmlns => 'https://xmlsql.XXXXX.xxx:441/'});
my $result = $soap->call($method => @.params);
unless ($result->fault) {
my $title = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/TITLE');
my $firstname = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/FIRST');
my $middlename = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/MIDDLE');
my $lastname = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/LAST');
my $suffix = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/SUFFIX');
my $address1 = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/STREET_ADDRESS');
my $address2 = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/ADDRESS2');
my $city = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/CITY');
my $stateprovince = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/STATE_PROV');
my $postalcode = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/ZIP');
my $country = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/COUNTRY');
my $homephone = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/HOME_PHONE');
my $workphone = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/WORK_PHONE');
my $emailaddress = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/EMAIL');
print "<font face=arial size=2><b>PIN Number:</b> $pin</font><br>";
print "<font face=arial size=2><b>Password:</b> $password</font><br>";
print "<font face=arial size=2><b>Title:</b> $title</font><br>";
print "<font face=arial size=2><b>First Name:</b> $firstname</font><br>";
print "<font face=arial size=2><b>Middle Name:</b> $middlename</font><br>";
print "<font face=arial size=2><b>Last Name:</b> $lastname</font><br>";
print "<font face=arial size=2><b>Suffix:</b> $suffix</font><br>";
print "<font face=arial size=2><b>Address1:</b> $address1</font><br>";
print "<font face=arial size=2><b>Address2:</b> $address2</font><br>";
print "<font face=arial size=2><b>City:</b> $city</font><br>";
print "<font face=arial size=2><b>State:</b> $stateprovince</font><br>";
print "<font face=arial size=2><b>ZIP/Postal Code:</b> $postalcode</font><br>";
print "<font face=arial size=2><b>Country:</b> $country</font><br>";
print "<font face=arial size=2><b>Home Phone:</b> $homephone</font><br>";
print "<font face=arial size=2><b>Work Phone:</b> $workphone</font><br>";
print "<font face=arial size=2><b>Email Address:</b> $emailaddress</font>";
}
else {
print join ', ',
$result->faultcode,
$result->faultstring,
$result->faultdetail;
}
}
Here is a nice easy way to debug SSL issue with Windows 2003 that I discovered while working on SOAP projects.
1. Create batch file c:\ssltrace.cmd with following contents:
logman start http_ssl_trace -pf c:\guids.txt -o out.etl -ets
pause
logman stop http_ssl_trace -ets
tracerpt /y out.etl
notepad dumpfile.csv
2. Create file c:\guids.txt with following contents:
{1fbecc45-c060-4e7c-8a0e-0dbd6116181b} 0x000000FF 5 IIS: SSL Filter
{dd5ef90a-6398-47a4-ad34-4dcecdef795f} 0x000000FF 5 HTTP Service Trace
3. On the web service machine run c:\ssltrace.cmd to start tracing, then hit your web service with your POST. Once you are finished testing press the spacebar to in the ssltrace.cmd command window to stop tracing and display the trace file. You should see everything coming in and going out along with error codes, etc...
|||Hello Matt,
your Message was helpfull to solve a problem with tracing.
Could you please tell me where you get the information
{1fbecc45-c060-4e7c-8a0e-0dbd6116181b} 0x000000FF 5 IIS: SSL Filter
{dd5ef90a-6398-47a4-ad34-4dcecdef795f} 0x000000FF 5 HTTP Service Trace
from?
Thanks
str01014
|||Actually I updated my batch file to inline everything (i've included it below).
To get a list of trace providers, run this ->
C:\>logman query providers
Provider GUID
-
...
IIS: SSL Filter {1fbecc45-c060-4e7c-8a0e-0dbd6116181b}
...
HTTP Service Trace {dd5ef90a-6398-47a4-ad34-4dcecdef795f}.
...
This will list each trace provider and it's GUID. The 2nd and 3rd values are flags passed to the trace provider to turn on and off various traces. How these values are used are provider specific. However if you just want to turn on all the flags pass in 0xFFFFFFFF and 255 like in my example below. Search MSDN for HTTP Service Trace and SSL Filter for information on what these flags do.
Here is my updated batch file (note it requires logparser tool which is downloadable from Microsoft) ->
rem START SSL TRACE DEMO
if exist ssltrace.guids del ssltrace.guids
echo {1fbecc45-c060-4e7c-8a0e-0dbd6116181b} 0xFFFFFFFF 255 IIS: SSL Filter >> ssltrace.guids
echo {dd5ef90a-6398-47a4-ad34-4dcecdef795f} 0xFFFFFFFF 255 HTTP Service Trace >> ssltrace.guids
logman start ssltrace -pf ssltrace.guids -o out.etl -ets
rem PRESS <SPACEBAR> TO STOP SSL+HTTP TRACING AND VIEW RESULTS
pause
logman stop ssltrace -ets
if exist ssltrace.guids del ssltrace.guids
if exist ssltrace.log del ssltrace.log
logparser -i:ETW "select * from out.etl" -e:ON >> ssltrace.log
start notepad ssltrace.log
rem END SSL TRACE DEMO
Help with SOAP Lite client error problems - CGI code
Hi,
I have been working on a soap client project for over a week now and can not figure out what I am doing wrong. I am not an expert using Perl or SOAP so any help would be "greatly" appreciated.
I get basic errors throughout, starting with:
Error - SOAP::Transport::HTTP::Client::send_receive: POST
It seems as if the user access information is not carried through as it should, but I truly have no idea what the problem is.
Here is what I have put together so far.
Thanks,
Mark
sub procgetmemberinfo {
my $pin = "$form{'lPin'}";
my $password = "$form{'sPassword'}";
my $soap = SOAP::Lite
-> uri('https://xmlsql.XXXXX.xxx:441')
-> on_action( sub { join '/', 'https://xmlsql.XXXXX.xxx:441', $_[1] } )
-> proxy('https://xmlsql.XXXXX.xxx:441/service.asmx?WSDL');
my @.params = (
SOAP::Data->name(lPin => $pin),
SOAP::Data->name(sPassword => $password)
);
my $method = SOAP::Data->name('GetMemberInfo')->attr({xmlns => 'https://xmlsql.XXXXX.xxx:441/'});
my $result = $soap->call($method => @.params);
unless ($result->fault) {
my $title = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/TITLE');
my $firstname = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/FIRST');
my $middlename = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/MIDDLE');
my $lastname = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/LAST');
my $suffix = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/SUFFIX');
my $address1 = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/STREET_ADDRESS');
my $address2 = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/ADDRESS2');
my $city = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/CITY');
my $stateprovince = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/STATE_PROV');
my $postalcode = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/ZIP');
my $country = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/COUNTRY');
my $homephone = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/HOME_PHONE');
my $workphone = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/WORK_PHONE');
my $emailaddress = $result->valueof('//GetMemberInfoResult/diffgram/NewDataSet/MEMBERS/EMAIL');
print "<font face=arial size=2><b>PIN Number:</b> $pin</font><br>";
print "<font face=arial size=2><b>Password:</b> $password</font><br>";
print "<font face=arial size=2><b>Title:</b> $title</font><br>";
print "<font face=arial size=2><b>First Name:</b> $firstname</font><br>";
print "<font face=arial size=2><b>Middle Name:</b> $middlename</font><br>";
print "<font face=arial size=2><b>Last Name:</b> $lastname</font><br>";
print "<font face=arial size=2><b>Suffix:</b> $suffix</font><br>";
print "<font face=arial size=2><b>Address1:</b> $address1</font><br>";
print "<font face=arial size=2><b>Address2:</b> $address2</font><br>";
print "<font face=arial size=2><b>City:</b> $city</font><br>";
print "<font face=arial size=2><b>State:</b> $stateprovince</font><br>";
print "<font face=arial size=2><b>ZIP/Postal Code:</b> $postalcode</font><br>";
print "<font face=arial size=2><b>Country:</b> $country</font><br>";
print "<font face=arial size=2><b>Home Phone:</b> $homephone</font><br>";
print "<font face=arial size=2><b>Work Phone:</b> $workphone</font><br>";
print "<font face=arial size=2><b>Email Address:</b> $emailaddress</font>";
}
else {
print join ', ',
$result->faultcode,
$result->faultstring,
$result->faultdetail;
}
}
Here is a nice easy way to debug SSL issue with Windows 2003 that I discovered while working on SOAP projects.
1. Create batch file c:\ssltrace.cmd with following contents:
logman start http_ssl_trace -pf c:\guids.txt -o out.etl -ets
pause
logman stop http_ssl_trace -ets
tracerpt /y out.etl
notepad dumpfile.csv
2. Create file c:\guids.txt with following contents:
{1fbecc45-c060-4e7c-8a0e-0dbd6116181b} 0x000000FF 5 IIS: SSL Filter
{dd5ef90a-6398-47a4-ad34-4dcecdef795f} 0x000000FF 5 HTTP Service Trace
3. On the web service machine run c:\ssltrace.cmd to start tracing, then hit your web service with your POST. Once you are finished testing press the spacebar to in the ssltrace.cmd command window to stop tracing and display the trace file. You should see everything coming in and going out along with error codes, etc...
|||Hello Matt,
your Message was helpfull to solve a problem with tracing.
Could you please tell me where you get the information
{1fbecc45-c060-4e7c-8a0e-0dbd6116181b} 0x000000FF 5 IIS: SSL Filter
{dd5ef90a-6398-47a4-ad34-4dcecdef795f} 0x000000FF 5 HTTP Service Trace
from?
Thanks
str01014
|||Actually I updated my batch file to inline everything (i've included it below).
To get a list of trace providers, run this ->
C:\>logman query providers
Provider GUID
-
...
IIS: SSL Filter {1fbecc45-c060-4e7c-8a0e-0dbd6116181b}
...
HTTP Service Trace {dd5ef90a-6398-47a4-ad34-4dcecdef795f}.
...
This will list each trace provider and it's GUID. The 2nd and 3rd values are flags passed to the trace provider to turn on and off various traces. How these values are used are provider specific. However if you just want to turn on all the flags pass in 0xFFFFFFFF and 255 like in my example below. Search MSDN for HTTP Service Trace and SSL Filter for information on what these flags do.
Here is my updated batch file (note it requires logparser tool which is downloadable from Microsoft) ->
rem START SSL TRACE DEMO
if exist ssltrace.guids del ssltrace.guids
echo {1fbecc45-c060-4e7c-8a0e-0dbd6116181b} 0xFFFFFFFF 255 IIS: SSL Filter >> ssltrace.guids
echo {dd5ef90a-6398-47a4-ad34-4dcecdef795f} 0xFFFFFFFF 255 HTTP Service Trace >> ssltrace.guids
logman start ssltrace -pf ssltrace.guids -o out.etl -ets
rem PRESS <SPACEBAR> TO STOP SSL+HTTP TRACING AND VIEW RESULTS
pause
logman stop ssltrace -ets
if exist ssltrace.guids del ssltrace.guids
if exist ssltrace.log del ssltrace.log
logparser -i:ETW "select * from out.etl" -e:ON >> ssltrace.log
start notepad ssltrace.log
rem END SSL TRACE DEMO
Friday, March 9, 2012
Help with Projected Plan Amounts
Project Plan Tables
I have an office yealy plan table, that is mostly static. Will I need to make this table a fact table and break this yearly plan number down by day using the time dimension to use it to calculate against all the facts in my fact table?
I have a fact table with all my daily submitted $ amounts per day, per office. I have a static "yearly office plan" table with my $$ per office per year. The thing is this "yearly office plan amount" could change based on business or sales and marketing decisions. I use this plan amount along with my fact table to base many mdx calculations against actuals vs plan, per day, per month etc.
FactPolicyTable has
DimOfficeTable has OfficeCode(key) and additional office information
PlanOffice table has keys of Plan_Office_Code(FK from OfficeCode), Plan_Office_Year, Plan Office Annual_Amt
The PlanOffice Annual Amt is what I need help with, how could I best implement this? all indications are I would have to break it down by day and move it into the FactPolicyTable or make it a fact table with a FK TimeKey in it. By the way this amount does not really relate to the PolicyNumber key in the fact table either.
I hope this gives you more to work with to help with my issue.
Or
Can I make this yearly plan amount a KPI? would the KPI still need to be broken down by day? can I use the KPI in to do calculations against other values in FactPolicy table?
What would be the best way to implement this Plan Value?
I hope I explained enough for this to make sense?
Well, the PlanOffice table could be a fact table for another measure group, which relates to the date dimension at a different granularity (ie. year) than does the FactPolicyTable (day). For example, in Adventure Works, the Sales Targets measure group relates to the Date dimension at the Calendar Quarter granularity, but [Measures].[Sales Amount Quota] gets allocated down to the month level in the cube MDX script.
Help with Projected Plan Amounts
Project Plan Tables
I have an office yealy plan table, that is mostly static. Will I need to make this table a fact table and break this yearly plan number down by day using the time dimension to use it to calculate against all the facts in my fact table?
I have a fact table with all my daily submitted $ amounts per day, per office. I have a static "yearly office plan" table with my $$ per office per year. The thing is this "yearly office plan amount" could change based on business or sales and marketing decisions. I use this plan amount along with my fact table to base many mdx calculations against actuals vs plan, per day, per month etc.
FactPolicyTable has
DimOfficeTable has OfficeCode(key) and additional office information
PlanOffice table has keys of Plan_Office_Code(FK from OfficeCode), Plan_Office_Year, Plan Office Annual_Amt
The PlanOffice Annual Amt is what I need help with, how could I best implement this? all indications are I would have to break it down by day and move it into the FactPolicyTable or make it a fact table with a FK TimeKey in it. By the way this amount does not really relate to the PolicyNumber key in the fact table either.
I hope this gives you more to work with to help with my issue.
Or
Can I make this yearly plan amount a KPI? would the KPI still need to be broken down by day? can I use the KPI in to do calculations against other values in FactPolicy table?
What would be the best way to implement this Plan Value?
I hope I explained enough for this to make sense?
Well, the PlanOffice table could be a fact table for another measure group, which relates to the date dimension at a different granularity (ie. year) than does the FactPolicyTable (day). For example, in Adventure Works, the Sales Targets measure group relates to the Date dimension at the Calendar Quarter granularity, but [Measures].[Sales Amount Quota] gets allocated down to the month level in the cube MDX script.Wednesday, March 7, 2012
Help with ordering the SSIS packages the way they appear in the project
In solution explorer under SSIS Packages there are many packages. I name them specifically so that they should be ordered with their names, but no the solution explorer shows them in the order I added them, I couldn't figure out a way but removing all the packages and adding them in the right order to fix that problem. I have to kinda redo this if I want to add a new package not to the end.
Any ideas?
All here: http://solidqualitylearning.com/blogs/erik/archive/2005/08/08/1269.aspx
-Jamie
|||Thank you, I didn't want to edit the configuration without knowing what I was doing.
Subscribe to:
Posts (Atom)