sql nulls slow: article

Showing posts with label article. Show all posts

Saturday, February 25, 2012

articles on sql 2005

Not an article, but the book Pro SQL Server 2005 is the best I've found thus
far to show all the new features.
ISBN: 1-59059-477-0
"noam" <imss@.netvision.net.il> wrote in message
news:1150633683.695303.17100@.y41g2000cwy.googlegroups.com...
> Hi all
> i'm looking for good articles to learned about administration and
> develope on sql 2005
> Thanks
>Hi all
i'm looking for good articles to learned about administration and
develope on sql 2005
Thanks|||Not an article, but the book Pro SQL Server 2005 is the best I've found thus
far to show all the new features.
ISBN: 1-59059-477-0
"noam" <imss@.netvision.net.il> wrote in message
news:1150633683.695303.17100@.y41g2000cwy.googlegroups.com...
> Hi all
> i'm looking for good articles to learned about administration and
> develope on sql 2005
> Thanks
>

Articles in more than one Category - How to organize tables?

Greetings,
I have one table, named Article, and one table name Category.
The problem is, one Article could be in just one or in several categories.
What is the best way to connect data between Article and Category according to fast search performance?
I have several ideas:
1. To have third cross table Article_Category with fields Article_ID and Category_ID, and search Article_Category table
2. To have several INTEGER columns in Article table (like Category_ID1, Category_ID2,..) and search those columns
3. Add one VARCHAR field in Article table where I could write Category ID's delimited by some character (e.g. by comma), and do text search in only that column.
What is recommended for solving problems like this?

Option 1 makes the most sense. This is how many-to-many relationships are generally implemented.

|||Thanks for advice Adam|||Yes, that is how I implemented them, it works well. Then you can use an inner join to join the article info to the category info.|||

Will you have:
Option A: Many-to-Many (category 1 has article 1 and 2, category 2 has article 3, etc)

Option B: 1-to-Many (Category 1 has article 2, category 2 has article 2, category 3 has article 5, etc)
If B, you can put your article_id in your category table. This would give you the fastest search performance and allow your joins to be simpler.

Nick

|||Hi bmains,
how large are your tables?
Do you run it on Web with ASP.NET?
Do you satisfied with search speed?|||Hi Nick,
one Category will have many articles,
one Article could be in more than one category.

There is 500 000 articles and almost 2000 categories.
Regards|||

If you are talking a join between the join table and the two main tables, then no, I wouldn't worry about speed; it shouldn't be worse performance-wise. Though, if you are talking a lot of joins, then you need to worry more. outer joins are worse than inner joins; inner joins aren't bad; here we have a requirement that you have to try to rewrite a query to use an inner join if possible, when an outer join is used.

articles about data access using System.Data.SqlClient namespace?

Aaarrgghhhhhhh, still searchin' for a nice step-by-step article to learn data access (all insert delete update commands) with the SQL Server .NET Data Provider found in [System.Data.SqlClient] namespace...

Can anyone plz help me to find it?these might help?
http://samples.gotdotnet.com/quickstart/howto/doc/adoplus/ADOPlusOverview.aspx
http://www.stylusinc.net/technology/microsoft/ado.shtml
http://msdn.microsoft.com/library/en-us/cpref/html/frlrfSystemDataSqlClientSqlConnectionClassTopic.asp?frame=true
http://msdn.microsoft.com/data/downloads/samples/default.aspx

Also
Check out the Data Access Application Block for .NET, it creates a wrapper around SqlClient class for somewhat easier use.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/daab-rm.asp

Article: Database Mirroring Not Ready for Production When SQL Server 2005 Ships

Can someone at Microsoft comment on this article, specifically, how it relates to SQL Replication? Will SQL Replication fall into the category of what this article describes, or only the mirroring feature?

Thanks,
PeterYes, Database Mirroring won't be available when SQL Server 2005 ships. Please refer to this: http://www.microsoft.com/sql/2005/productinfo/letter.mspx. However this does not affect replication at all.

article row filter - 2 parameters

hello,

i need to filter an article based on a user-supplied datetime filter (the datetime parameter is specified by the subscriber just before replication). at the same time i need to filter again by user (different subscribers get different rows).

i already did the user-based filter using HOST_NAME( ). but the difficulty here (al least i think so) lies in passing 2 parameters to the filter. i cannot rely on using SUSER_SNAME to pass the user filter, because no one will want to create 500 user accounts. so i guess the only solution here is to pass both parameters using only HOST_NAME( ) and then write 2 splitting functions which uses HOST_NAME( ) as its parameter. am i right ?

publisher/distributor is sql server 2005, all subscribers use sql mobile.

TIA, kamil nowicki

Using datetime would not be recommended since it is not deterministic.

For eg:

lets say you have a filter to get rows being touched only in the last 7 days.

Initially you get all rows.

After 7 days having not touched any rows, you would expect the merge agent deletes the 7 rows which will not be the case.

I would advise you to use SUSER_SNAME() or HOST_NAME() to get specific rows and in addition use another column 'status' or something that you can set/reset according to your business needs.

|||

thanks for replying.

i think that i have to use a datetime filter because the parameter to this filter has to be dynamic (worst case scenario: each subscriber uses different filter parameter for each of his replication sessions). is there another way to accomplish this ?

also, is there a way to store something in SUSER_SNAME() like using SqlCeReplication.HostName to store something into HOSTNAME() ?

|||

If each session of the subscriber uses a different filter, you will get an error with mismatched partitions. You would need to reinitialize the subscriber in that case. Are you ready to reinitialize the subscribers for every sync?

But note that as I mentioned previously, you will not be able to rely on datetime filter. Use a status column or something like that and update this column when you want rows to be in partition or out of partition.

|||

>> Use a status column or something like that and update this column when you want rows to be in partition or out of partition.

but that would mean that i have to use a "fixed filter" (same "replicate from ..." date for every subscriber), wouldn't it ?

|||How about: login=SUSER_SNAME and status='Y'|||

We have a best practice article for time-based filtering, you may want to reference it, it's what Mahesh is talking about:

Best Practices for Time-Based Row Filters

http://msdn2.microsoft.com/en-us/library/ms365153.aspx

|||

and how does that solve my scenario ? i want each subscriber to be able to choose a date ( "replicate from..." ) before each of his replication sessions. SP on the server will not know those dates when executed, so how am i supposed to update the "status" column ?

thanks for the link, i have read that before starting the thread.

|||

Are you saying that every time the subscriber syncs, it sends a new date and expects only releant rows? You cannot achieve this using the non-deterministic filter functions. If you are ready to reinitialize your subscriptions every time you sync, you may do that. Do a reinit on the publisher/subscriber, then send in the appropriate date as the hostname to get the relevant rows. However you wont be able to upload in this session because your filters may not match data that you want to upload.

|||

i took a different approach and now everything is working as it should. i wrote a SP on the backend server which updates every row in the filtered article for a given user (SP is parametrized with @.user nvarchar and @.filter datetime), changing rep_status tinyint column. the SP is called from subscriber on the distributor just before each replication session, so now the SP has all the info to update the filtered article (@.user and @.filter). article is filtered by rep_status.

the drawback is that the backend has to be put out of LAN to the internet (public IP), but later i will write a WebService so that all the data will pass through IIS and then the backend will be again NATed.

edit: and of course this works without subscription reinitialization :)

article request

can anybody tell me a useful online article,site or a book, to know about SQL
server internalsOn Thu, 13 Oct 2005 02:07:03 -0700, "enbee"
<enbee@.discussions.microsoft.com> wrote:
>can anybody tell me a useful online article,site or a book, to know about SQL
>server internals
You could do a lot worse than Kalen Delaney's book Inside SQL Server
2000.
If you are referrring to SQL Server 2005 I believe an updated edition
is in preparation.
Andrew Watt
MVP - InfoPath|||Inside Microsoft SQL Server 2000
http://vyaskn.tripod.com/inside_microsoft_sql_server_2000.htm
Also, "The Guru's Guide to SQL Server Architecture and Internals"
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"enbee" <enbee@.discussions.microsoft.com> wrote in message
news:9E5DBA88-D015-47FF-AC47-44AFFA4936CB@.microsoft.com...
can anybody tell me a useful online article,site or a book, to know about
SQL
server internals|||SQL Server magazine puts out a CD every 6 months with the latest and
greatest. Kalen Delaney, as one person noted, is certainly an authority on
SQL Server and there are loads of articles she's written. I use it
frequently and often and every chance I get.
A years subscription (which includes online access to SQL Server magazine)
is about $60.
Cheers.
HTH
"enbee" wrote:
> can anybody tell me a useful online article,site or a book, to know about SQL
> server internals

article request

can anybody tell me a useful online article,site or a book, to know about SQL
server internals
On Thu, 13 Oct 2005 02:07:03 -0700, "enbee"
<enbee@.discussions.microsoft.com> wrote:

>can anybody tell me a useful online article,site or a book, to know about SQL
>server internals
You could do a lot worse than Kalen Delaney's book Inside SQL Server
2000.
If you are referrring to SQL Server 2005 I believe an updated edition
is in preparation.
Andrew Watt
MVP - InfoPath
|||Inside Microsoft SQL Server 2000
http://vyaskn.tripod.com/inside_micr...erver_2000.htm
Also, "The Guru's Guide to SQL Server Architecture and Internals"
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"enbee" <enbee@.discussions.microsoft.com> wrote in message
news:9E5DBA88-D015-47FF-AC47-44AFFA4936CB@.microsoft.com...
can anybody tell me a useful online article,site or a book, to know about
SQL
server internals
|||SQL Server magazine puts out a CD every 6 months with the latest and
greatest. Kalen Delaney, as one person noted, is certainly an authority on
SQL Server and there are loads of articles she's written. I use it
frequently and often and every chance I get.
A years subscription (which includes online access to SQL Server magazine)
is about $60.
Cheers.
HTH
"enbee" wrote:

> can anybody tell me a useful online article,site or a book, to know about SQL
> server internals

article request

can anybody tell me a useful online article,site or a book, to know about SQ
L
server internalsOn Thu, 13 Oct 2005 02:07:03 -0700, "enbee"
<enbee@.discussions.microsoft.com> wrote:

>can anybody tell me a useful online article,site or a book, to know about S
QL
>server internals
You could do a lot worse than Kalen Delaney's book Inside SQL Server
2000.
If you are referrring to SQL Server 2005 I believe an updated edition
is in preparation.
Andrew Watt
MVP - InfoPath|||Inside Microsoft SQL Server 2000
http://vyaskn.tripod.com/inside_mic...server_2000.htm
Also, "The Guru's Guide to SQL Server Architecture and Internals"
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"enbee" <enbee@.discussions.microsoft.com> wrote in message
news:9E5DBA88-D015-47FF-AC47-44AFFA4936CB@.microsoft.com...
can anybody tell me a useful online article,site or a book, to know about
SQL
server internals|||SQL Server magazine puts out a CD every 6 months with the latest and
greatest. Kalen Delaney, as one person noted, is certainly an authority on
SQL Server and there are loads of articles she's written. I use it
frequently and often and every chance I get.
A years subscription (which includes online access to SQL Server magazine)
is about $60.
Cheers.
HTH
"enbee" wrote:

> can anybody tell me a useful online article,site or a book, to know about
SQL
> server internals

article or some good reasons to kick devs out of production

>Let me know what should i tell them so I can revoke their access
>Thanks
>
-- AntiSpam/harvest --
Remove X's to send email to me.
|||A hammer, baseball bat, or golf club come to mind. So does, "I'm
responsible for it now". There isn't an easy answer. This is pure politics
that can really be argued both ways. My basic answer is that unless someone
is going to be held accountable for maintaining a database, they shouldn't
have any administrative authority. "Just in case" is just an excuse for
"please don't take away my toys".
I usually fix it by simply handing developers a pager. When they ask what
that is for, I tell them that since they have access to the production
database, that also make them responsible for it. Since they are
responsible for it, they also have to carry a pager and be woken up at 3AM
when things go wrong. Access is usually revoked within a day of doing that.

Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Hassan" <Hassan@.hotmail.com> wrote in message
news:uK3TO8hJGHA.740@.TK2MSFTNGP12.phx.gbl...
> My devs all have access to production. They always had and they feel they
> should still just in case they need to resolve issues.
> Are there any articles on how I can convince them to get out and stay out
>

Let me know what should i tell them so I can revoke their access
> Thanks
>
|||:-)
I like your style. I may have to try that myself (it's an ongoing issue
where I work - I'm pretty solid on the SQL side of things but not great
on the political side of things).
*mike hodgson*
http://sqlnerd.blogspot.com
Michael Hotek wrote:

>A hammer, baseball bat, or golf club come to mind. So does, "I'm
>responsible for it now". There isn't an easy answer. This is pure politics
>that can really be argued both ways. My basic answer is that unless someone
>is going to be held accountable for maintaining a database, they shouldn't
>have any administrative authority. "Just in case" is just an excuse for
>"please don't take away my toys".
>I usually fix it by simply handing developers a pager. When they ask what
>that is for, I tell them that since they have access to the production
>database, that also make them responsible for it. Since they are
>responsible for it, they also have to carry a pager and be woken up at 3AM
>when things go wrong. Access is usually revoked within a day of doing that.
>

>
>
|||You can state several reason, and that depend upon
1. criticality of your data
- If some dev, run an update and mess up your data you need to restore
last back up and transaction log just before update happend. Then you need to
keep your server offline, will that affect your business? then thats a good
reason.
2. Size of your data
- If data is huge, restoration of corrupt data can take much time
3. Routine maintenece
- As admin you got routine maintenece , also you may go for process
where DB should be in single user mode.
Again why cant you go for an arhictecture where you have
=> Development Server
=> Integrated Server
=> Prodcution Server
Take daily backup from production, and restore it in Integrated Server. Give
dev access to integrated server, so that they will get the recent data from
production. Do the fix and apply that in production.
Thanks,
Sree
"Michael Hotek" wrote:

> A hammer, baseball bat, or golf club come to mind. So does, "I'm
> responsible for it now". There isn't an easy answer. This is pure politics
> that can really be argued both ways. My basic answer is that unless someone
> is going to be held accountable for maintaining a database, they shouldn't
> have any administrative authority. "Just in case" is just an excuse for
> "please don't take away my toys".
> I usually fix it by simply handing developers a pager. When they ask what
> that is for, I tell them that since they have access to the production
> database, that also make them responsible for it. Since they are
> responsible for it, they also have to carry a pager and be woken up at 3AM
> when things go wrong. Access is usually revoked within a day of doing that.
>

> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:uK3TO8hJGHA.740@.TK2MSFTNGP12.phx.gbl...
>
>
|||Hi Mike
Something that I don't think has been specifically mentioned is
accountability, it is not the same as trust, because you can give developers
access to the production system but only in a contolled manner, and only to
make changes that have been passed as fit i.e. been through the a test cycle.
The other thing is sensitivity, the more open the access is, then the
greater the risk of a violation. Whoever carries this risk should be aware of
the situation.
If your developers do not have access to a production system, there should
be an equivalent system that can be used if the need arises. If your data is
sensitive, then this alternative system can be de-sensitized.
John
"Mike Hodgson" wrote:

> :-)
> I like your style. I may have to try that myself (it's an ongoing issue
> where I work - I'm pretty solid on the SQL side of things but not great
> on the political side of things).
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Michael Hotek wrote:
>
|||That's really the basic point behind handing developers a pager or whatever
you use. People always seem to want administrative access to things without
having any of the responsibility. You simply make it a point that if they
want admin access, of any kind, then they are going to be just as
responsible for the system as you are. That means every time something goes
wrong on the system, they get yanked into it right along with everyone else.
The rest is left unsaid, because it doesn't need to be. It's making a very
fine point about why certain people have admin access and no one else does
without getting into a big argument about it.
When you boil it all down, there isn't a single reason that someone can come
up with that I couldn't argue both sides of. It has nothing to do with data
volume, operations that are executed, errors that are found, change control,
etc.
The only issue that can't be argued is responsiblity. If you have admin
access, that means you are responsible for the system, period. If you give
someone admin access without also requiring them to be responsible for the
system, then you might as well get used to sleeping in your office.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:57A3D790-44EB-403E-AFEB-7CC922094886@.microsoft.com...[vbcol=seagreen]
> Hi Mike
> Something that I don't think has been specifically mentioned is
> accountability, it is not the same as trust, because you can give
> developers
> access to the production system but only in a contolled manner, and only
> to
> make changes that have been passed as fit i.e. been through the a test
> cycle.
> The other thing is sensitivity, the more open the access is, then the
> greater the risk of a violation. Whoever carries this risk should be aware
> of
> the situation.
> If your developers do not have access to a production system, there should
> be an equivalent system that can be used if the need arises. If your data
> is
> sensitive, then this alternative system can be de-sensitized.
> John
>
> "Mike Hodgson" wrote:
|||Hi Mike
I think what I was pointing out was from the other direction, the developers
may want access to the company payrole, but will whoever is responsible for
it want them to have it? I.e. you may need to find the person who is
responsible and say "Do you want them to do this?"
John
"Michael Hotek" wrote:

> That's really the basic point behind handing developers a pager or whatever
> you use. People always seem to want administrative access to things without
> having any of the responsibility. You simply make it a point that if they
> want admin access, of any kind, then they are going to be just as
> responsible for the system as you are. That means every time something goes
> wrong on the system, they get yanked into it right along with everyone else.
> The rest is left unsaid, because it doesn't need to be. It's making a very
> fine point about why certain people have admin access and no one else does
> without getting into a big argument about it.
> When you boil it all down, there isn't a single reason that someone can come
> up with that I couldn't argue both sides of. It has nothing to do with data
> volume, operations that are executed, errors that are found, change control,
> etc.
> The only issue that can't be argued is responsiblity. If you have admin
> access, that means you are responsible for the system, period. If you give
> someone admin access without also requiring them to be responsible for the
> system, then you might as well get used to sleeping in your office.
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:57A3D790-44EB-403E-AFEB-7CC922094886@.microsoft.com...
>
>
|||On Mon, 30 Jan 2006 20:30:23 -0800, Hassan wrote:

>My devs all have access to production. They always had and they feel they
>should still just in case they need to resolve issues.
>Are there any articles on how I can convince them to get out and stay out

>Let me know what should i tell them so I can revoke their access
>Thanks
>
Hi Hassan,
A lot of good ideas are mentioned already. But I've missed one so far:
in many countries, privacy laws require you to limit access to
production data to only those who absolutely need it. Developers don't
need permanent access to production data.
(They may sometimes need temp access to prod when troubleshooting a
production error - they should use a special login that is normally
disabled, fully logged, and they should ideally be constantly monitored
while fixing the problem - though the last requirement is somewhat
unrealistic).
Hugo Kornelis, SQL Server MVP
|||I understand, that's a much different issue that's really easy to fix. When
you have sensitive data, that's a simple case to restrict access that no one
can argue with. It's the cases that don't fall into that category that are
more difficult.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:2A73DAF3-A001-4927-94D7-051852672CA3@.microsoft.com...[vbcol=seagreen]
> Hi Mike
> I think what I was pointing out was from the other direction, the
> developers
> may want access to the company payrole, but will whoever is responsible
> for
> it want them to have it? I.e. you may need to find the person who is
> responsible and say "Do you want them to do this?"
> John
> "Michael Hotek" wrote:

article or some good reasons to kick devs out of production

Let me know what should i tell them so I can revoke their access
Thanksif you don't trust someone; hand them specifically what you want them to wor
k on
and nothing else.
I've worked on *MANY* large scale production systems. I've never had "100%
access to 100% of the project".
If they're your devs, "here's the way it is".
I recently pointed out a small bug in an application. would take 2 seconds t
o
fix. (typo in a dialog).
I am *NOT* to change anything w/o a bug being written up & published.
It was, but said "do not change it unless you're working on that module for
something else".
The problem will be there for upwards of 3+ months because that module is ro
ck
solid. Point? it's what I was told to do as a developer.
Tell your devs they'll get access to what they need.
Now; once you do -- live wit hthe fact that things don't happen as fast and
the
backlash of "I couldn't resolve the issue, so-and-so had rights, not me." Y
ou
will have created the situation.
On Mon, 30 Jan 2006 20:30:23 -0800, "Hassan" <Hassan@.hotmail.com> wrote:

>My devs all have access to production. They always had and they feel they
>should still just in case they need to resolve issues.
>Are there any articles on how I can convince them to get out and stay out :
)
>Let me know what should i tell them so I can revoke their access
>Thanks
>
-- AntiSpam/harvest --
Remove X's to send email to me.|||A hammer, baseball bat, or golf club come to mind. So does, "I'm
responsible for it now". There isn't an easy answer. This is pure politics
that can really be argued both ways. My basic answer is that unless someone
is going to be held accountable for maintaining a database, they shouldn't
have any administrative authority. "Just in case" is just an excuse for
"please don't take away my toys".
I usually fix it by simply handing developers a pager. When they ask what
that is for, I tell them that since they have access to the production
database, that also make them responsible for it. Since they are
responsible for it, they also have to carry a pager and be woken up at 3AM
when things go wrong. Access is usually revoked within a day of doing that.

Let me know what should i tell them so I can revoke their access
> Thanks
>|||:-)
I like your style. I may have to try that myself (it's an ongoing issue
where I work - I'm pretty solid on the SQL side of things but not great
on the political side of things).
*mike hodgson*
http://sqlnerd.blogspot.com
Michael Hotek wrote:

>A hammer, baseball bat, or golf club come to mind. So does, "I'm
>responsible for it now". There isn't an easy answer. This is pure politic
s
>that can really be argued both ways. My basic answer is that unless someon
e
>is going to be held accountable for maintaining a database, they shouldn't
>have any administrative authority. "Just in case" is just an excuse for
>"please don't take away my toys".
>I usually fix it by simply handing developers a pager. When they ask what
>that is for, I tell them that since they have access to the production
>database, that also make them responsible for it. Since they are
>responsible for it, they also have to carry a pager and be woken up at 3AM
>when things go wrong. Access is usually revoked within a day of doing that
.
>

>
>|||You can state several reason, and that depend upon
1. criticality of your data
- If some dev, run an update and mess up your data you need to restore
last back up and transaction log just before update happend. Then you need t
o
keep your server offline, will that affect your business? then thats a good
reason.
2. Size of your data
- If data is huge, restoration of corrupt data can take much time
3. Routine maintenece
- As admin you got routine maintenece , also you may go for process
where DB should be in single user mode.
Again why cant you go for an arhictecture where you have
=> Development Server
=> Integrated Server
=> Prodcution Server
Take daily backup from production, and restore it in Integrated Server. Give
dev access to integrated server, so that they will get the recent data from
production. Do the fix and apply that in production.
Thanks,
Sree
"Michael Hotek" wrote:

> A hammer, baseball bat, or golf club come to mind. So does, "I'm
> responsible for it now". There isn't an easy answer. This is pure politi
cs
> that can really be argued both ways. My basic answer is that unless someo
ne
> is going to be held accountable for maintaining a database, they shouldn't
> have any administrative authority. "Just in case" is just an excuse for
> "please don't take away my toys".
> I usually fix it by simply handing developers a pager. When they ask what
> that is for, I tell them that since they have access to the production
> database, that also make them responsible for it. Since they are
> responsible for it, they also have to carry a pager and be woken up at 3AM
> when things go wrong. Access is usually revoked within a day of doing tha
t.
>

> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:uK3TO8hJGHA.740@.TK2MSFTNGP12.phx.gbl...
>
>|||Hi Mike
Something that I don't think has been specifically mentioned is
accountability, it is not the same as trust, because you can give developers
access to the production system but only in a contolled manner, and only to
make changes that have been passed as fit i.e. been through the a test cycle
.
The other thing is sensitivity, the more open the access is, then the
greater the risk of a violation. Whoever carries this risk should be aware o
f
the situation.
If your developers do not have access to a production system, there should
be an equivalent system that can be used if the need arises. If your data is
sensitive, then this alternative system can be de-sensitized.
John
"Mike Hodgson" wrote:

> :-)
> I like your style. I may have to try that myself (it's an ongoing issue
> where I work - I'm pretty solid on the SQL side of things but not great
> on the political side of things).
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Michael Hotek wrote:
>
>|||That's really the basic point behind handing developers a pager or whatever
you use. People always seem to want administrative access to things without
having any of the responsibility. You simply make it a point that if they
want admin access, of any kind, then they are going to be just as
responsible for the system as you are. That means every time something goes
wrong on the system, they get yanked into it right along with everyone else.
The rest is left unsaid, because it doesn't need to be. It's making a very
fine point about why certain people have admin access and no one else does
without getting into a big argument about it.
When you boil it all down, there isn't a single reason that someone can come
up with that I couldn't argue both sides of. It has nothing to do with data
volume, operations that are executed, errors that are found, change control,
etc.
The only issue that can't be argued is responsiblity. If you have admin
access, that means you are responsible for the system, period. If you give
someone admin access without also requiring them to be responsible for the
system, then you might as well get used to sleeping in your office.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:57A3D790-44EB-403E-AFEB-7CC922094886@.microsoft.com...[vbcol=seagreen]
> Hi Mike
> Something that I don't think has been specifically mentioned is
> accountability, it is not the same as trust, because you can give
> developers
> access to the production system but only in a contolled manner, and only
> to
> make changes that have been passed as fit i.e. been through the a test
> cycle.
> The other thing is sensitivity, the more open the access is, then the
> greater the risk of a violation. Whoever carries this risk should be aware
> of
> the situation.
> If your developers do not have access to a production system, there should
> be an equivalent system that can be used if the need arises. If your data
> is
> sensitive, then this alternative system can be de-sensitized.
> John
>
> "Mike Hodgson" wrote:
>|||Hi Mike
I think what I was pointing out was from the other direction, the developers
may want access to the company payrole, but will whoever is responsible for
it want them to have it? I.e. you may need to find the person who is
responsible and say "Do you want them to do this?"
John
"Michael Hotek" wrote:

> That's really the basic point behind handing developers a pager or whateve
r
> you use. People always seem to want administrative access to things witho
ut
> having any of the responsibility. You simply make it a point that if they
> want admin access, of any kind, then they are going to be just as
> responsible for the system as you are. That means every time something go
es
> wrong on the system, they get yanked into it right along with everyone els
e.
> The rest is left unsaid, because it doesn't need to be. It's making a ver
y
> fine point about why certain people have admin access and no one else does
> without getting into a big argument about it.
> When you boil it all down, there isn't a single reason that someone can co
me
> up with that I couldn't argue both sides of. It has nothing to do with da
ta
> volume, operations that are executed, errors that are found, change contro
l,
> etc.
> The only issue that can't be argued is responsiblity. If you have admin
> access, that means you are responsible for the system, period. If you giv
e
> someone admin access without also requiring them to be responsible for the
> system, then you might as well get used to sleeping in your office.
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:57A3D790-44EB-403E-AFEB-7CC922094886@.microsoft.com...
>
>|||On Mon, 30 Jan 2006 20:30:23 -0800, Hassan wrote:

>My devs all have access to production. They always had and they feel they
>should still just in case they need to resolve issues.
>Are there any articles on how I can convince them to get out and stay out :
)
>Let me know what should i tell them so I can revoke their access
>Thanks
>
Hi Hassan,
A lot of good ideas are mentioned already. But I've missed one so far:
in many countries, privacy laws require you to limit access to
production data to only those who absolutely need it. Developers don't
need permanent access to production data.
(They may sometimes need temp access to prod when troubleshooting a
production error - they should use a special login that is normally
disabled, fully logged, and they should ideally be constantly monitored
while fixing the problem - though the last requirement is somewhat
unrealistic).
Hugo Kornelis, SQL Server MVP|||I understand, that's a much different issue that's really easy to fix. When
you have sensitive data, that's a simple case to restrict access that no one
can argue with. It's the cases that don't fall into that category that are
more difficult.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:2A73DAF3-A001-4927-94D7-051852672CA3@.microsoft.com...[vbcol=seagreen]
> Hi Mike
> I think what I was pointing out was from the other direction, the
> developers
> may want access to the company payrole, but will whoever is responsible
> for
> it want them to have it? I.e. you may need to find the person who is
> responsible and say "Do you want them to do this?"
> John
> "Michael Hotek" wrote:
>

article or some good reasons to kick devs out of production

My devs all have access to production. They always had and they feel they
should still just in case they need to resolve issues.
Are there any articles on how I can convince them to get out and stay out :)
Let me know what should i tell them so I can revoke their access
Thanksif you don't trust someone; hand them specifically what you want them to work on
and nothing else.
I've worked on *MANY* large scale production systems. I've never had "100%
access to 100% of the project".
If they're your devs, "here's the way it is".
I recently pointed out a small bug in an application. would take 2 seconds to
fix. (typo in a dialog).
I am *NOT* to change anything w/o a bug being written up & published.
It was, but said "do not change it unless you're working on that module for
something else".
The problem will be there for upwards of 3+ months because that module is rock
solid. Point? it's what I was told to do as a developer.
Tell your devs they'll get access to what they need.
Now; once you do -- live wit hthe fact that things don't happen as fast and the
backlash of "I couldn't resolve the issue, so-and-so had rights, not me." You
will have created the situation.
On Mon, 30 Jan 2006 20:30:23 -0800, "Hassan" <Hassan@.hotmail.com> wrote:
>My devs all have access to production. They always had and they feel they
>should still just in case they need to resolve issues.
>Are there any articles on how I can convince them to get out and stay out :)
>Let me know what should i tell them so I can revoke their access
>Thanks
>
-- AntiSpam/harvest --
Remove X's to send email to me.|||A hammer, baseball bat, or golf club come to mind. So does, "I'm
responsible for it now". There isn't an easy answer. This is pure politics
that can really be argued both ways. My basic answer is that unless someone
is going to be held accountable for maintaining a database, they shouldn't
have any administrative authority. "Just in case" is just an excuse for
"please don't take away my toys".
I usually fix it by simply handing developers a pager. When they ask what
that is for, I tell them that since they have access to the production
database, that also make them responsible for it. Since they are
responsible for it, they also have to carry a pager and be woken up at 3AM
when things go wrong. Access is usually revoked within a day of doing that.
:)
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Hassan" <Hassan@.hotmail.com> wrote in message
news:uK3TO8hJGHA.740@.TK2MSFTNGP12.phx.gbl...
> My devs all have access to production. They always had and they feel they
> should still just in case they need to resolve issues.
> Are there any articles on how I can convince them to get out and stay out
> :) Let me know what should i tell them so I can revoke their access
> Thanks
>|||This is a multi-part message in MIME format.
--080209070300040309090905
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
:-)
I like your style. I may have to try that myself (it's an ongoing issue
where I work - I'm pretty solid on the SQL side of things but not great
on the political side of things).
--
*mike hodgson*
http://sqlnerd.blogspot.com
Michael Hotek wrote:
>A hammer, baseball bat, or golf club come to mind. So does, "I'm
>responsible for it now". There isn't an easy answer. This is pure politics
>that can really be argued both ways. My basic answer is that unless someone
>is going to be held accountable for maintaining a database, they shouldn't
>have any administrative authority. "Just in case" is just an excuse for
>"please don't take away my toys".
>I usually fix it by simply handing developers a pager. When they ask what
>that is for, I tell them that since they have access to the production
>database, that also make them responsible for it. Since they are
>responsible for it, they also have to carry a pager and be woken up at 3AM
>when things go wrong. Access is usually revoked within a day of doing that.
>:)
>
>
--080209070300040309090905
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt> :-) 
 
I like your style. I may have to try that myself (it's an ongoing
issue where I work - I'm pretty solid on the SQL side of things but not
great on the political side of things).</tt> 
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
-- 
 mike
hodgson 
<a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a>

</div>
 
 
Michael Hotek wrote:
<blockquote cite="midOc1oMQiJGHA.3144@.TK2MSFTNGP11.phx.gbl" type="cite">
<pre wrap="">A hammer, baseball bat, or golf club come to mind. So does, "I'm
responsible for it now". There isn't an easy answer. This is pure politics
that can really be argued both ways. My basic answer is that unless someone
is going to be held accountable for maintaining a database, they shouldn't
have any administrative authority. "Just in case" is just an excuse for
"please don't take away my toys".
I usually fix it by simply handing developers a pager. When they ask what
that is for, I tell them that since they have access to the production
database, that also make them responsible for it. Since they are
responsible for it, they also have to carry a pager and be woken up at 3AM
when things go wrong. Access is usually revoked within a day of doing that.
:)
</pre>
</blockquote>
</body>
</html>
--080209070300040309090905--|||You can state several reason, and that depend upon
1. criticality of your data
- If some dev, run an update and mess up your data you need to restore
last back up and transaction log just before update happend. Then you need to
keep your server offline, will that affect your business? then thats a good
reason.
2. Size of your data
- If data is huge, restoration of corrupt data can take much time
3. Routine maintenece
- As admin you got routine maintenece , also you may go for process
where DB should be in single user mode.
Again why cant you go for an arhictecture where you have
=> Development Server
=> Integrated Server
=> Prodcution Server
Take daily backup from production, and restore it in Integrated Server. Give
dev access to integrated server, so that they will get the recent data from
production. Do the fix and apply that in production.
Thanks,
Sree
"Michael Hotek" wrote:
> A hammer, baseball bat, or golf club come to mind. So does, "I'm
> responsible for it now". There isn't an easy answer. This is pure politics
> that can really be argued both ways. My basic answer is that unless someone
> is going to be held accountable for maintaining a database, they shouldn't
> have any administrative authority. "Just in case" is just an excuse for
> "please don't take away my toys".
> I usually fix it by simply handing developers a pager. When they ask what
> that is for, I tell them that since they have access to the production
> database, that also make them responsible for it. Since they are
> responsible for it, they also have to carry a pager and be woken up at 3AM
> when things go wrong. Access is usually revoked within a day of doing that.
> :)
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:uK3TO8hJGHA.740@.TK2MSFTNGP12.phx.gbl...
> > My devs all have access to production. They always had and they feel they
> > should still just in case they need to resolve issues.
> >
> > Are there any articles on how I can convince them to get out and stay out
> > :) Let me know what should i tell them so I can revoke their access
> >
> > Thanks
> >
>
>|||Hi Mike
Something that I don't think has been specifically mentioned is
accountability, it is not the same as trust, because you can give developers
access to the production system but only in a contolled manner, and only to
make changes that have been passed as fit i.e. been through the a test cycle.
The other thing is sensitivity, the more open the access is, then the
greater the risk of a violation. Whoever carries this risk should be aware of
the situation.
If your developers do not have access to a production system, there should
be an equivalent system that can be used if the need arises. If your data is
sensitive, then this alternative system can be de-sensitized.
John
"Mike Hodgson" wrote:
> :-)
> I like your style. I may have to try that myself (it's an ongoing issue
> where I work - I'm pretty solid on the SQL side of things but not great
> on the political side of things).
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Michael Hotek wrote:
> >A hammer, baseball bat, or golf club come to mind. So does, "I'm
> >responsible for it now". There isn't an easy answer. This is pure politics
> >that can really be argued both ways. My basic answer is that unless someone
> >is going to be held accountable for maintaining a database, they shouldn't
> >have any administrative authority. "Just in case" is just an excuse for
> >"please don't take away my toys".
> >
> >I usually fix it by simply handing developers a pager. When they ask what
> >that is for, I tell them that since they have access to the production
> >database, that also make them responsible for it. Since they are
> >responsible for it, they also have to carry a pager and be woken up at 3AM
> >when things go wrong. Access is usually revoked within a day of doing that.
> >:)
> >
> >
> >
>|||That's really the basic point behind handing developers a pager or whatever
you use. People always seem to want administrative access to things without
having any of the responsibility. You simply make it a point that if they
want admin access, of any kind, then they are going to be just as
responsible for the system as you are. That means every time something goes
wrong on the system, they get yanked into it right along with everyone else.
The rest is left unsaid, because it doesn't need to be. It's making a very
fine point about why certain people have admin access and no one else does
without getting into a big argument about it.
When you boil it all down, there isn't a single reason that someone can come
up with that I couldn't argue both sides of. It has nothing to do with data
volume, operations that are executed, errors that are found, change control,
etc.
The only issue that can't be argued is responsiblity. If you have admin
access, that means you are responsible for the system, period. If you give
someone admin access without also requiring them to be responsible for the
system, then you might as well get used to sleeping in your office.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:57A3D790-44EB-403E-AFEB-7CC922094886@.microsoft.com...
> Hi Mike
> Something that I don't think has been specifically mentioned is
> accountability, it is not the same as trust, because you can give
> developers
> access to the production system but only in a contolled manner, and only
> to
> make changes that have been passed as fit i.e. been through the a test
> cycle.
> The other thing is sensitivity, the more open the access is, then the
> greater the risk of a violation. Whoever carries this risk should be aware
> of
> the situation.
> If your developers do not have access to a production system, there should
> be an equivalent system that can be used if the need arises. If your data
> is
> sensitive, then this alternative system can be de-sensitized.
> John
>
> "Mike Hodgson" wrote:
>> :-)
>> I like your style. I may have to try that myself (it's an ongoing issue
>> where I work - I'm pretty solid on the SQL side of things but not great
>> on the political side of things).
>> --
>> *mike hodgson*
>> http://sqlnerd.blogspot.com
>>
>> Michael Hotek wrote:
>> >A hammer, baseball bat, or golf club come to mind. So does, "I'm
>> >responsible for it now". There isn't an easy answer. This is pure
>> >politics
>> >that can really be argued both ways. My basic answer is that unless
>> >someone
>> >is going to be held accountable for maintaining a database, they
>> >shouldn't
>> >have any administrative authority. "Just in case" is just an excuse for
>> >"please don't take away my toys".
>> >
>> >I usually fix it by simply handing developers a pager. When they ask
>> >what
>> >that is for, I tell them that since they have access to the production
>> >database, that also make them responsible for it. Since they are
>> >responsible for it, they also have to carry a pager and be woken up at
>> >3AM
>> >when things go wrong. Access is usually revoked within a day of doing
>> >that.
>> >:)
>> >
>> >
>> >|||Hi Mike
I think what I was pointing out was from the other direction, the developers
may want access to the company payrole, but will whoever is responsible for
it want them to have it? I.e. you may need to find the person who is
responsible and say "Do you want them to do this?"
John
"Michael Hotek" wrote:
> That's really the basic point behind handing developers a pager or whatever
> you use. People always seem to want administrative access to things without
> having any of the responsibility. You simply make it a point that if they
> want admin access, of any kind, then they are going to be just as
> responsible for the system as you are. That means every time something goes
> wrong on the system, they get yanked into it right along with everyone else.
> The rest is left unsaid, because it doesn't need to be. It's making a very
> fine point about why certain people have admin access and no one else does
> without getting into a big argument about it.
> When you boil it all down, there isn't a single reason that someone can come
> up with that I couldn't argue both sides of. It has nothing to do with data
> volume, operations that are executed, errors that are found, change control,
> etc.
> The only issue that can't be argued is responsiblity. If you have admin
> access, that means you are responsible for the system, period. If you give
> someone admin access without also requiring them to be responsible for the
> system, then you might as well get used to sleeping in your office.
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:57A3D790-44EB-403E-AFEB-7CC922094886@.microsoft.com...
> > Hi Mike
> >
> > Something that I don't think has been specifically mentioned is
> > accountability, it is not the same as trust, because you can give
> > developers
> > access to the production system but only in a contolled manner, and only
> > to
> > make changes that have been passed as fit i.e. been through the a test
> > cycle.
> >
> > The other thing is sensitivity, the more open the access is, then the
> > greater the risk of a violation. Whoever carries this risk should be aware
> > of
> > the situation.
> >
> > If your developers do not have access to a production system, there should
> > be an equivalent system that can be used if the need arises. If your data
> > is
> > sensitive, then this alternative system can be de-sensitized.
> >
> > John
> >
> >
> >
> > "Mike Hodgson" wrote:
> >
> >> :-)
> >>
> >> I like your style. I may have to try that myself (it's an ongoing issue
> >> where I work - I'm pretty solid on the SQL side of things but not great
> >> on the political side of things).
> >>
> >> --
> >> *mike hodgson*
> >> http://sqlnerd.blogspot.com
> >>
> >>
> >>
> >> Michael Hotek wrote:
> >>
> >> >A hammer, baseball bat, or golf club come to mind. So does, "I'm
> >> >responsible for it now". There isn't an easy answer. This is pure
> >> >politics
> >> >that can really be argued both ways. My basic answer is that unless
> >> >someone
> >> >is going to be held accountable for maintaining a database, they
> >> >shouldn't
> >> >have any administrative authority. "Just in case" is just an excuse for
> >> >"please don't take away my toys".
> >> >
> >> >I usually fix it by simply handing developers a pager. When they ask
> >> >what
> >> >that is for, I tell them that since they have access to the production
> >> >database, that also make them responsible for it. Since they are
> >> >responsible for it, they also have to carry a pager and be woken up at
> >> >3AM
> >> >when things go wrong. Access is usually revoked within a day of doing
> >> >that.
> >> >:)
> >> >
> >> >
> >> >
> >>
>
>|||On Mon, 30 Jan 2006 20:30:23 -0800, Hassan wrote:
>My devs all have access to production. They always had and they feel they
>should still just in case they need to resolve issues.
>Are there any articles on how I can convince them to get out and stay out :)
>Let me know what should i tell them so I can revoke their access
>Thanks
>
Hi Hassan,
A lot of good ideas are mentioned already. But I've missed one so far:
in many countries, privacy laws require you to limit access to
production data to only those who absolutely need it. Developers don't
need permanent access to production data.
(They may sometimes need temp access to prod when troubleshooting a
production error - they should use a special login that is normally
disabled, fully logged, and they should ideally be constantly monitored
while fixing the problem - though the last requirement is somewhat
unrealistic).
--
Hugo Kornelis, SQL Server MVP|||I understand, that's a much different issue that's really easy to fix. When
you have sensitive data, that's a simple case to restrict access that no one
can argue with. It's the cases that don't fall into that category that are
more difficult.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:2A73DAF3-A001-4927-94D7-051852672CA3@.microsoft.com...
> Hi Mike
> I think what I was pointing out was from the other direction, the
> developers
> may want access to the company payrole, but will whoever is responsible
> for
> it want them to have it? I.e. you may need to find the person who is
> responsible and say "Do you want them to do this?"
> John
> "Michael Hotek" wrote:
>> That's really the basic point behind handing developers a pager or
>> whatever
>> you use. People always seem to want administrative access to things
>> without
>> having any of the responsibility. You simply make it a point that if
>> they
>> want admin access, of any kind, then they are going to be just as
>> responsible for the system as you are. That means every time something
>> goes
>> wrong on the system, they get yanked into it right along with everyone
>> else.
>> The rest is left unsaid, because it doesn't need to be. It's making a
>> very
>> fine point about why certain people have admin access and no one else
>> does
>> without getting into a big argument about it.
>> When you boil it all down, there isn't a single reason that someone can
>> come
>> up with that I couldn't argue both sides of. It has nothing to do with
>> data
>> volume, operations that are executed, errors that are found, change
>> control,
>> etc.
>> The only issue that can't be argued is responsiblity. If you have admin
>> access, that means you are responsible for the system, period. If you
>> give
>> someone admin access without also requiring them to be responsible for
>> the
>> system, then you might as well get used to sleeping in your office.
>> --
>> Mike
>> http://www.solidqualitylearning.com
>> Disclaimer: This communication is an original work and represents my sole
>> views on the subject. It does not represent the views of any other
>> person
>> or entity either by inference or direct reference.
>>
>> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
>> news:57A3D790-44EB-403E-AFEB-7CC922094886@.microsoft.com...
>> > Hi Mike
>> >
>> > Something that I don't think has been specifically mentioned is
>> > accountability, it is not the same as trust, because you can give
>> > developers
>> > access to the production system but only in a contolled manner, and
>> > only
>> > to
>> > make changes that have been passed as fit i.e. been through the a test
>> > cycle.
>> >
>> > The other thing is sensitivity, the more open the access is, then the
>> > greater the risk of a violation. Whoever carries this risk should be
>> > aware
>> > of
>> > the situation.
>> >
>> > If your developers do not have access to a production system, there
>> > should
>> > be an equivalent system that can be used if the need arises. If your
>> > data
>> > is
>> > sensitive, then this alternative system can be de-sensitized.
>> >
>> > John
>> >
>> >
>> >
>> > "Mike Hodgson" wrote:
>> >
>> >> :-)
>> >>
>> >> I like your style. I may have to try that myself (it's an ongoing
>> >> issue
>> >> where I work - I'm pretty solid on the SQL side of things but not
>> >> great
>> >> on the political side of things).
>> >>
>> >> --
>> >> *mike hodgson*
>> >> http://sqlnerd.blogspot.com
>> >>
>> >>
>> >>
>> >> Michael Hotek wrote:
>> >>
>> >> >A hammer, baseball bat, or golf club come to mind. So does, "I'm
>> >> >responsible for it now". There isn't an easy answer. This is pure
>> >> >politics
>> >> >that can really be argued both ways. My basic answer is that unless
>> >> >someone
>> >> >is going to be held accountable for maintaining a database, they
>> >> >shouldn't
>> >> >have any administrative authority. "Just in case" is just an excuse
>> >> >for
>> >> >"please don't take away my toys".
>> >> >
>> >> >I usually fix it by simply handing developers a pager. When they ask
>> >> >what
>> >> >that is for, I tell them that since they have access to the
>> >> >production
>> >> >database, that also make them responsible for it. Since they are
>> >> >responsible for it, they also have to carry a pager and be woken up
>> >> >at
>> >> >3AM
>> >> >when things go wrong. Access is usually revoked within a day of
>> >> >doing
>> >> >that.
>> >> >:)
>> >> >
>> >> >
>> >> >
>> >>
>>

article on Windows 2003 + sql

I came across an article long time ago and cannot seem to track it now.
It talked about the advantages of migrating your SQL 2000 from Windows 2000
to windows 2003.
Can someone who knows about this, send me a linkHi
I don't know of any SQL Server specific articles, but you will gain all the
generic advantages from using this version:
Top 10:
http://tinyurl.com/bqnx
Why upgrade:
http://tinyurl.com/2u2j9
Performance comparison:
http://tinyurl.com/x7ma
Upgrade site:
http://tinyurl.com/2yhgj
Analyst reports:
http://tinyurl.com/8fnxj
Background:
http://tinyurl.com/adhaf
John
"Hassan" wrote:
> I came across an article long time ago and cannot seem to track it now.
> It talked about the advantages of migrating your SQL 2000 from Windows 2000
> to windows 2003.
> Can someone who knows about this, send me a link
>
>

article on Windows 2003 + sql

I came across an article long time ago and cannot seem to track it now.
It talked about the advantages of migrating your SQL 2000 from Windows 2000
to windows 2003.
Can someone who knows about this, send me a link
Hi
I don't know of any SQL Server specific articles, but you will gain all the
generic advantages from using this version:
Top 10:
http://tinyurl.com/bqnx
Why upgrade:
http://tinyurl.com/2u2j9
Performance comparison:
http://tinyurl.com/x7ma
Upgrade site:
http://tinyurl.com/2yhgj
Analyst reports:
http://tinyurl.com/8fnxj
Background:
http://tinyurl.com/adhaf
John
"Hassan" wrote:

> I came across an article long time ago and cannot seem to track it now.
> It talked about the advantages of migrating your SQL 2000 from Windows 2000
> to windows 2003.
> Can someone who knows about this, send me a link
>
>

article on Windows 2003 + sql

I came across an article long time ago and cannot seem to track it now.
It talked about the advantages of migrating your SQL 2000 from Windows 2000
to windows 2003.
Can someone who knows about this, send me a linkHi
I don't know of any SQL Server specific articles, but you will gain all the
generic advantages from using this version:
Top 10:
http://tinyurl.com/bqnx
Why upgrade:
http://tinyurl.com/2u2j9
Performance comparison:
http://tinyurl.com/x7ma
Upgrade site:
http://tinyurl.com/2yhgj
Analyst reports:
http://tinyurl.com/8fnxj
Background:
http://tinyurl.com/adhaf
John
"Hassan" wrote:

> I came across an article long time ago and cannot seem to track it now.
> It talked about the advantages of migrating your SQL 2000 from Windows 200
0
> to windows 2003.
> Can someone who knows about this, send me a link
>
>

Article on when to use Stored Procs?

Does anybody know of some good articles or whitepapers on when to use stored
procs and when not to use them? Thanks in advance.
DaveHere is a compact artilce along with some good discussion:
http://weblogs.asp.net/rhoward/arch...1/17/38095.aspx
"Dave L" wrote:

> Does anybody know of some good articles or whitepapers on when to use stor
ed
> procs and when not to use them? Thanks in advance.
> Dave
>|||> Does anybody know of some good articles or whitepapers on when to use
> stored
> procs and when not to use them? Thanks in advance.
Thus saith the LORD GOD: "Thou shalt use stored procedures for everything,
and for everything shalt thou use them."
Seriously. Here are some:
http://weblogs.asp.net/rhoward/arch...1/17/38095.aspx
http://www.devx.com/tips/Tip/13175
http://www.csharpfriends.com/Articl...px?articleID=78
Peace & happy computing,
Mike Labosh, MCSD
"When you kill a man, you're a murderer.
Kill many, and you're a conqueror.
Kill them all and you're a god." -- Dave Mustane

article on the optimiser generating a query plan

Is there a nice article on where i can find out how the query optimiser
chooses a query plan and what kind a plan it might choose with some examples
?
Whether it may use nested loop joins or merge or hash , whether it will do a
table scan, Clustered Index scan or seek.,etc...Take a look at:
http://msdn.microsoft.com/library/default.asp?url=/nhp/default.asp?contentid=28000409
and
http://msdn.microsoft.com/library/default.asp?url=/nhp/default.asp?contentid=28000409
--
Hal Berenson, SQL Server MVP
True Mountain Group LLC
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:uX8$UyFbDHA.1940@.TK2MSFTNGP10.phx.gbl...
> Is there a nice article on where i can find out how the query optimiser
> chooses a query plan and what kind a plan it might choose with some
examples
> ?
> Whether it may use nested loop joins or merge or hash , whether it will do
a
> table scan, Clustered Index scan or seek.,etc...
>|||The 2 URLs are the same. Is that a generic place u sent me to about SQL
Server or is there a specific article out there
"Hal Berenson" <haroldb@.truemountainconsulting.com> wrote in message
news:uIj1A3FbDHA.2024@.TK2MSFTNGP12.phx.gbl...
> Take a look at:
>
http://msdn.microsoft.com/library/default.asp?url=/nhp/default.asp?contentid=28000409
> and
>
http://msdn.microsoft.com/library/default.asp?url=/nhp/default.asp?contentid=28000409
> --
> Hal Berenson, SQL Server MVP
> True Mountain Group LLC
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:uX8$UyFbDHA.1940@.TK2MSFTNGP10.phx.gbl...
> > Is there a nice article on where i can find out how the query optimiser
> > chooses a query plan and what kind a plan it might choose with some
> examples
> > ?
> > Whether it may use nested loop joins or merge or hash , whether it will
do
> a
> > table scan, Clustered Index scan or seek.,etc...
> >
> >
>|||Superb... I havent read it though but it looks like what i was looking for.
When is part 8 due ? Do you have all that clubbed together somehow for an
easy print ?
Good Luck to u
"joe chang" <jchang6@.yahoo.com> wrote in message
news:0e5d01c36cb4$6583dec0$a601280a@.phx.gbl...
> http://www.sql-server-
> performance.com/jc_sql_server_quantative_analysis1.asp
>
> >--Original Message--
> >Is there a nice article on where i can find out how the
> query optimiser
> >chooses a query plan and what kind a plan it might choose
> with some examples
> >?
> >Whether it may use nested loop joins or merge or hash ,
> whether it will do a
> >table scan, Clustered Index scan or seek.,etc...
> >
> >
> >.
> >|||Hassan,
MS SQL Server Performance Tuning and Optimization for Developers, Part 2:
The Query Optimizer
http://www.microsoft.com/technet/prodtechnol/sql/maintain/optimize/dat411.asp?frame=true
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:uX8$UyFbDHA.1940@.TK2MSFTNGP10.phx.gbl...
> Is there a nice article on where i can find out how the query optimiser
> chooses a query plan and what kind a plan it might choose with some
examples
> ?
> Whether it may use nested loop joins or merge or hash , whether it will do
a
> table scan, Clustered Index scan or seek.,etc...
>|||Is that good enough for SQL 2000 ? It says Tech-Ed 97.. Can you confirm ?
"Dinesh.T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:%23gjaEuNbDHA.2820@.tk2msftngp13.phx.gbl...
> Hassan,
> MS SQL Server Performance Tuning and Optimization for Developers, Part 2:
> The Query Optimizer
>
http://www.microsoft.com/technet/prodtechnol/sql/maintain/optimize/dat411.asp?frame=true
> --
> Dinesh.
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:uX8$UyFbDHA.1940@.TK2MSFTNGP10.phx.gbl...
> > Is there a nice article on where i can find out how the query optimiser
> > chooses a query plan and what kind a plan it might choose with some
> examples
> > ?
> > Whether it may use nested loop joins or merge or hash , whether it will
do
> a
> > table scan, Clustered Index scan or seek.,etc...
> >
> >
>|||Hassan,
Except some basic stuff, I dont believe it holds good for SQL2000
considering the presentation date and the author not explictly stating the
SQL Server version.
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:eKkSoMObDHA.1204@.TK2MSFTNGP12.phx.gbl...
> Is that good enough for SQL 2000 ? It says Tech-Ed 97.. Can you confirm ?
> "Dinesh.T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
> news:%23gjaEuNbDHA.2820@.tk2msftngp13.phx.gbl...
> > Hassan,
> >
> > MS SQL Server Performance Tuning and Optimization for Developers, Part
2:
> > The Query Optimizer
> >
>
http://www.microsoft.com/technet/prodtechnol/sql/maintain/optimize/dat411.asp?frame=true
> >
> > --
> > Dinesh.
> > SQL Server FAQ at
> > http://www.tkdinesh.com
> >
> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
> > news:uX8$UyFbDHA.1940@.TK2MSFTNGP10.phx.gbl...
> > > Is there a nice article on where i can find out how the query
optimiser
> > > chooses a query plan and what kind a plan it might choose with some
> > examples
> > > ?
> > > Whether it may use nested loop joins or merge or hash , whether it
will
> do
> > a
> > > table scan, Clustered Index scan or seek.,etc...
> > >
> > >
> >
> >
>|||This is a SQL Server 6.5 presentation and doesn't apply to SQL Server 7.0 or
2000.
The articles at
http://www.microsoft.com/technet/prodtechnol/sql/maintain/optimize/sql7qp.asp
and
http://msdn.microsoft.com/library/en-us/dnsql7/html/sqlquerproc.asp
were written for SQL Server 7.0 but are 90% accurate for SQL Server 2000 as
well.
--
Hal Berenson, SQL Server MVP
True Mountain Group LLC
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:eKkSoMObDHA.1204@.TK2MSFTNGP12.phx.gbl...
> Is that good enough for SQL 2000 ? It says Tech-Ed 97.. Can you confirm ?
> "Dinesh.T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
> news:%23gjaEuNbDHA.2820@.tk2msftngp13.phx.gbl...
> > Hassan,
> >
> > MS SQL Server Performance Tuning and Optimization for Developers, Part
2:
> > The Query Optimizer
> >
>
http://www.microsoft.com/technet/prodtechnol/sql/maintain/optimize/dat411.asp?frame=true
> >
> > --
> > Dinesh.
> > SQL Server FAQ at
> > http://www.tkdinesh.com
> >
> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
> > news:uX8$UyFbDHA.1940@.TK2MSFTNGP10.phx.gbl...
> > > Is there a nice article on where i can find out how the query
optimiser
> > > chooses a query plan and what kind a plan it might choose with some
> > examples
> > > ?
> > > Whether it may use nested loop joins or merge or hash , whether it
will
> do
> > a
> > > table scan, Clustered Index scan or seek.,etc...
> > >
> > >
> >
> >
>

Article on Speeding up your SQL Server Development with easy to use tools

http://www.aspalliance.com/349After considering the pros and cons we have decided to open the free SQL Scripts download to all users and not make them register on the website.

We do encourage people to register for future releases and more development tools to follow.

Also feedbacks are greatly appreciated.

You can visit http://www.etekglobalinc.com/DesktopDefault.aspx?tabid=68 to download the scripts.

Thanks,

Article on RS Forms Authentication - Part II

Here comes the second part. Learn how to implement role-membership and
troubleshoot custom security.
http://www.devx.com/dotnet/Article/27133/0/page/1
--
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---Hi Teo
I have succesfully implemented the FAuth in my reporting services , but my
problem is I cannot use the rs.exe publishreports.rss script to deploy
reports as it gives the follwoing error: could not connect to
http://ws034/reportserver/reportservice.asmx My understanding is because it
is not passing the sqlauth cokie and hence could not connect this is how I am
calling the script:
rs -i C:\PublishReports.rss -s http://ws034/ReportServer/reportservice.asmx
-u admin -p admin -v filePath="C:\unzipped\11946\Reports" -v
sqlServerName="ws034" -v parentFolder="ScriptUpload"
any assistance would be most appreciated.
thanks in advance
"Teo Lachev [MVP]" wrote:
> Here comes the second part. Learn how to implement role-membership and
> troubleshoot custom security.
> http://www.devx.com/dotnet/Article/27133/0/page/1
> --
> Hope this helps.
> ---
> Teo Lachev, MVP [SQL Server], MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> Publisher website: http://www.manning.com/lachev
> Buy it from Amazon.com: http://shrinkster.com/eq
> Home page and blog: http://www.prologika.com/
> ---
>
>|||Yes, this stems from the fact that the cookie is not supplied. Remember, you
have to call LogonUser first to get the cookie. You may find my WinForm
sample useful to find out how to maintain and send the cookie from a non-web
client.
http://prologika.com/blog/archive/2004/08/27/169.aspx
--
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"shahab" <shahab@.discussions.microsoft.com> wrote in message
news:88A44FCD-5BD2-494F-BBB5-0E86C95AA36F@.microsoft.com...
> Hi Teo
> I have succesfully implemented the FAuth in my reporting services , but my
> problem is I cannot use the rs.exe publishreports.rss script to deploy
> reports as it gives the follwoing error: could not connect to
> http://ws034/reportserver/reportservice.asmx My understanding is because
> it
> is not passing the sqlauth cokie and hence could not connect this is how I
> am
> calling the script:
> rs -i C:\PublishReports.rss -s
> http://ws034/ReportServer/reportservice.asmx
> -u admin -p admin -v filePath="C:\unzipped\11946\Reports" -v
> sqlServerName="ws034" -v parentFolder="ScriptUpload"
> any assistance would be most appreciated.
> thanks in advance
> "Teo Lachev [MVP]" wrote:
>> Here comes the second part. Learn how to implement role-membership and
>> troubleshoot custom security.
>> http://www.devx.com/dotnet/Article/27133/0/page/1
>> --
>> Hope this helps.
>> ---
>> Teo Lachev, MVP [SQL Server], MCSD, MCT
>> Author: "Microsoft Reporting Services in Action"
>> Publisher website: http://www.manning.com/lachev
>> Buy it from Amazon.com: http://shrinkster.com/eq
>> Home page and blog: http://www.prologika.com/
>> ---
>>|||"Teo Lachev [MVP]" <teo.lachev@.nospam.prologika.com> wrote in
news:eHxxOG7EFHA.2600@.TK2MSFTNGP09.phx.gbl:
> Yes, this stems from the fact that the cookie is not supplied.
> Remember, you have to call LogonUser first to get the cookie. You may
> find my WinForm sample useful to find out how to maintain and send the
> cookie from a non-web client.
> http://prologika.com/blog/archive/2004/08/27/169.aspx
>
I am trying to implement the role-based piece of the security extension in
a web farm environment. I think that I am having my issues because of the
use of "HttpContext.Current.Cache" -- would this be an issue in a web farm?
If so, do you have any alternatives other than to not cache the roles?
Thanks!|||I don't think caching will cause any issues. Basically, if the load balanced
server doesn't find the roles in its cache, it will load them from the data
store. So, you will end up with as many cached instances of the user roles
as the number of servers but this is just a performance optimization
technique and shouldn't be a problem.
That's said though, as the article mentiones, you should be aware of memory
constraints that caching may cause. For example, if you have thousands of
users, you may consider expiring the cache on a regular basis.
--
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"Jason A. Bentley" <jason_a_bentley@.hotmail.com> wrote in message
news:Xns95FF6B0C984EDjasonabentleyhotmail@.207.46.248.16...
> "Teo Lachev [MVP]" <teo.lachev@.nospam.prologika.com> wrote in
> news:eHxxOG7EFHA.2600@.TK2MSFTNGP09.phx.gbl:
>> Yes, this stems from the fact that the cookie is not supplied.
>> Remember, you have to call LogonUser first to get the cookie. You may
>> find my WinForm sample useful to find out how to maintain and send the
>> cookie from a non-web client.
>> http://prologika.com/blog/archive/2004/08/27/169.aspx
> I am trying to implement the role-based piece of the security extension in
> a web farm environment. I think that I am having my issues because of the
> use of "HttpContext.Current.Cache" -- would this be an issue in a web
> farm?
> If so, do you have any alternatives other than to not cache the roles?
> Thanks!|||I should've given more thought on this, Jason.
I forgot the fact that article code implements role caching in LogonUser.
This WILL present an issue with load balancing since LogonUser is called
once during the cookie lifetime and the custom extension will not find the
roles on the second server during user authorization (assuming that
authentication takes place on server one and the user is re-directed and
authorized on server two). So, one workaround is to move role caching to the
CheckOperations helper function in the Authorization extension. Another
workaround of course is to use sticky sessions.
Thanks for bringing this up.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"Teo Lachev [MVP]" <teo.lachev@.nospam.prologika.com> wrote in message
news:u1aseJKFFHA.2572@.tk2msftngp13.phx.gbl...
>I don't think caching will cause any issues. Basically, if the load
>balanced server doesn't find the roles in its cache, it will load them from
>the data store. So, you will end up with as many cached instances of the
>user roles as the number of servers but this is just a performance
>optimization technique and shouldn't be a problem.
> That's said though, as the article mentiones, you should be aware of
> memory constraints that caching may cause. For example, if you have
> thousands of users, you may consider expiring the cache on a regular
> basis.
> --
> Hope this helps.
> ---
> Teo Lachev, MVP [SQL Server], MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> Publisher website: http://www.manning.com/lachev
> Buy it from Amazon.com: http://shrinkster.com/eq
> Home page and blog: http://www.prologika.com/
> ---
> "Jason A. Bentley" <jason_a_bentley@.hotmail.com> wrote in message
> news:Xns95FF6B0C984EDjasonabentleyhotmail@.207.46.248.16...
>> "Teo Lachev [MVP]" <teo.lachev@.nospam.prologika.com> wrote in
>> news:eHxxOG7EFHA.2600@.TK2MSFTNGP09.phx.gbl:
>> Yes, this stems from the fact that the cookie is not supplied.
>> Remember, you have to call LogonUser first to get the cookie. You may
>> find my WinForm sample useful to find out how to maintain and send the
>> cookie from a non-web client.
>> http://prologika.com/blog/archive/2004/08/27/169.aspx
>>
>> I am trying to implement the role-based piece of the security extension
>> in
>> a web farm environment. I think that I am having my issues because of
>> the
>> use of "HttpContext.Current.Cache" -- would this be an issue in a web
>> farm?
>> If so, do you have any alternatives other than to not cache the roles?
>> Thanks!
>|||Teo thanks for your article I have successfully implemented the Forms based
authentication. My biggest problem now is I cannot run any reports that have
ORACLE datasource. It comes with an error that logon failed!
Do you know some workaround. Please any assistance would be most appreciated.
Thanks
============================================"Teo Lachev [MVP]" wrote:
> I should've given more thought on this, Jason.
> I forgot the fact that article code implements role caching in LogonUser.
> This WILL present an issue with load balancing since LogonUser is called
> once during the cookie lifetime and the custom extension will not find the
> roles on the second server during user authorization (assuming that
> authentication takes place on server one and the user is re-directed and
> authorized on server two). So, one workaround is to move role caching to the
> CheckOperations helper function in the Authorization extension. Another
> workaround of course is to use sticky sessions.
> Thanks for bringing this up.
> ---
> Teo Lachev, MVP [SQL Server], MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> Publisher website: http://www.manning.com/lachev
> Buy it from Amazon.com: http://shrinkster.com/eq
> Home page and blog: http://www.prologika.com/
> ---
> "Teo Lachev [MVP]" <teo.lachev@.nospam.prologika.com> wrote in message
> news:u1aseJKFFHA.2572@.tk2msftngp13.phx.gbl...
> >I don't think caching will cause any issues. Basically, if the load
> >balanced server doesn't find the roles in its cache, it will load them from
> >the data store. So, you will end up with as many cached instances of the
> >user roles as the number of servers but this is just a performance
> >optimization technique and shouldn't be a problem.
> >
> > That's said though, as the article mentiones, you should be aware of
> > memory constraints that caching may cause. For example, if you have
> > thousands of users, you may consider expiring the cache on a regular
> > basis.
> >
> > --
> > Hope this helps.
> >
> > ---
> > Teo Lachev, MVP [SQL Server], MCSD, MCT
> > Author: "Microsoft Reporting Services in Action"
> > Publisher website: http://www.manning.com/lachev
> > Buy it from Amazon.com: http://shrinkster.com/eq
> > Home page and blog: http://www.prologika.com/
> > ---
> >
> > "Jason A. Bentley" <jason_a_bentley@.hotmail.com> wrote in message
> > news:Xns95FF6B0C984EDjasonabentleyhotmail@.207.46.248.16...
> >> "Teo Lachev [MVP]" <teo.lachev@.nospam.prologika.com> wrote in
> >> news:eHxxOG7EFHA.2600@.TK2MSFTNGP09.phx.gbl:
> >>
> >> Yes, this stems from the fact that the cookie is not supplied.
> >> Remember, you have to call LogonUser first to get the cookie. You may
> >> find my WinForm sample useful to find out how to maintain and send the
> >> cookie from a non-web client.
> >>
> >> http://prologika.com/blog/archive/2004/08/27/169.aspx
> >>
> >>
> >> I am trying to implement the role-based piece of the security extension
> >> in
> >> a web farm environment. I think that I am having my issues because of
> >> the
> >> use of "HttpContext.Current.Cache" -- would this be an issue in a web
> >> farm?
> >> If so, do you have any alternatives other than to not cache the roles?
> >>
> >> Thanks!
> >
> >
>
>|||The report data source fails or the LogonUser fails? What kind of
authentication do you use?
--
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"shahab" <shahab@.discussions.microsoft.com> wrote in message
news:5E6A0C29-AB87-4B5E-A788-927A87003CFA@.microsoft.com...
> Teo thanks for your article I have successfully implemented the Forms
> based
> authentication. My biggest problem now is I cannot run any reports that
> have
> ORACLE datasource. It comes with an error that logon failed!
> Do you know some workaround. Please any assistance would be most
> appreciated.
> Thanks
>
> ============================================> "Teo Lachev [MVP]" wrote:
>> I should've given more thought on this, Jason.
>> I forgot the fact that article code implements role caching in LogonUser.
>> This WILL present an issue with load balancing since LogonUser is called
>> once during the cookie lifetime and the custom extension will not find
>> the
>> roles on the second server during user authorization (assuming that
>> authentication takes place on server one and the user is re-directed and
>> authorized on server two). So, one workaround is to move role caching to
>> the
>> CheckOperations helper function in the Authorization extension. Another
>> workaround of course is to use sticky sessions.
>> Thanks for bringing this up.
>> ---
>> Teo Lachev, MVP [SQL Server], MCSD, MCT
>> Author: "Microsoft Reporting Services in Action"
>> Publisher website: http://www.manning.com/lachev
>> Buy it from Amazon.com: http://shrinkster.com/eq
>> Home page and blog: http://www.prologika.com/
>> ---
>> "Teo Lachev [MVP]" <teo.lachev@.nospam.prologika.com> wrote in message
>> news:u1aseJKFFHA.2572@.tk2msftngp13.phx.gbl...
>> >I don't think caching will cause any issues. Basically, if the load
>> >balanced server doesn't find the roles in its cache, it will load them
>> >from
>> >the data store. So, you will end up with as many cached instances of the
>> >user roles as the number of servers but this is just a performance
>> >optimization technique and shouldn't be a problem.
>> >
>> > That's said though, as the article mentiones, you should be aware of
>> > memory constraints that caching may cause. For example, if you have
>> > thousands of users, you may consider expiring the cache on a regular
>> > basis.
>> >
>> > --
>> > Hope this helps.
>> >
>> > ---
>> > Teo Lachev, MVP [SQL Server], MCSD, MCT
>> > Author: "Microsoft Reporting Services in Action"
>> > Publisher website: http://www.manning.com/lachev
>> > Buy it from Amazon.com: http://shrinkster.com/eq
>> > Home page and blog: http://www.prologika.com/
>> > ---
>> >
>> > "Jason A. Bentley" <jason_a_bentley@.hotmail.com> wrote in message
>> > news:Xns95FF6B0C984EDjasonabentleyhotmail@.207.46.248.16...
>> >> "Teo Lachev [MVP]" <teo.lachev@.nospam.prologika.com> wrote in
>> >> news:eHxxOG7EFHA.2600@.TK2MSFTNGP09.phx.gbl:
>> >>
>> >> Yes, this stems from the fact that the cookie is not supplied.
>> >> Remember, you have to call LogonUser first to get the cookie. You may
>> >> find my WinForm sample useful to find out how to maintain and send
>> >> the
>> >> cookie from a non-web client.
>> >>
>> >> http://prologika.com/blog/archive/2004/08/27/169.aspx
>> >>
>> >>
>> >> I am trying to implement the role-based piece of the security
>> >> extension
>> >> in
>> >> a web farm environment. I think that I am having my issues because of
>> >> the
>> >> use of "HttpContext.Current.Cache" -- would this be an issue in a web
>> >> farm?
>> >> If so, do you have any alternatives other than to not cache the roles?
>> >>
>> >> Thanks!
>> >
>> >
>>|||thanks for your time. I managed to get it working, what I did was that I
uninstalled RS ,uninstalled the Oracle 9.1 client and then reinstalled Oracle
client and RS respectively. for some reason the RS was not identifying the
existence of Oracle on my machine maybe I installed Oracle client after the
RS was installed.
"Teo Lachev [MVP]" wrote:
> The report data source fails or the LogonUser fails? What kind of
> authentication do you use?
> --
> Hope this helps.
> ---
> Teo Lachev, MVP [SQL Server], MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> Publisher website: http://www.manning.com/lachev
> Buy it from Amazon.com: http://shrinkster.com/eq
> Home page and blog: http://www.prologika.com/
> ---
> "shahab" <shahab@.discussions.microsoft.com> wrote in message
> news:5E6A0C29-AB87-4B5E-A788-927A87003CFA@.microsoft.com...
> > Teo thanks for your article I have successfully implemented the Forms
> > based
> > authentication. My biggest problem now is I cannot run any reports that
> > have
> > ORACLE datasource. It comes with an error that logon failed!
> > Do you know some workaround. Please any assistance would be most
> > appreciated.
> > Thanks
> >
> >
> > ============================================> > "Teo Lachev [MVP]" wrote:
> >
> >> I should've given more thought on this, Jason.
> >>
> >> I forgot the fact that article code implements role caching in LogonUser.
> >> This WILL present an issue with load balancing since LogonUser is called
> >> once during the cookie lifetime and the custom extension will not find
> >> the
> >> roles on the second server during user authorization (assuming that
> >> authentication takes place on server one and the user is re-directed and
> >> authorized on server two). So, one workaround is to move role caching to
> >> the
> >> CheckOperations helper function in the Authorization extension. Another
> >> workaround of course is to use sticky sessions.
> >>
> >> Thanks for bringing this up.
> >>
> >> ---
> >> Teo Lachev, MVP [SQL Server], MCSD, MCT
> >> Author: "Microsoft Reporting Services in Action"
> >> Publisher website: http://www.manning.com/lachev
> >> Buy it from Amazon.com: http://shrinkster.com/eq
> >> Home page and blog: http://www.prologika.com/
> >> ---
> >>
> >> "Teo Lachev [MVP]" <teo.lachev@.nospam.prologika.com> wrote in message
> >> news:u1aseJKFFHA.2572@.tk2msftngp13.phx.gbl...
> >> >I don't think caching will cause any issues. Basically, if the load
> >> >balanced server doesn't find the roles in its cache, it will load them
> >> >from
> >> >the data store. So, you will end up with as many cached instances of the
> >> >user roles as the number of servers but this is just a performance
> >> >optimization technique and shouldn't be a problem.
> >> >
> >> > That's said though, as the article mentiones, you should be aware of
> >> > memory constraints that caching may cause. For example, if you have
> >> > thousands of users, you may consider expiring the cache on a regular
> >> > basis.
> >> >
> >> > --
> >> > Hope this helps.
> >> >
> >> > ---
> >> > Teo Lachev, MVP [SQL Server], MCSD, MCT
> >> > Author: "Microsoft Reporting Services in Action"
> >> > Publisher website: http://www.manning.com/lachev
> >> > Buy it from Amazon.com: http://shrinkster.com/eq
> >> > Home page and blog: http://www.prologika.com/
> >> > ---
> >> >
> >> > "Jason A. Bentley" <jason_a_bentley@.hotmail.com> wrote in message
> >> > news:Xns95FF6B0C984EDjasonabentleyhotmail@.207.46.248.16...
> >> >> "Teo Lachev [MVP]" <teo.lachev@.nospam.prologika.com> wrote in
> >> >> news:eHxxOG7EFHA.2600@.TK2MSFTNGP09.phx.gbl:
> >> >>
> >> >> Yes, this stems from the fact that the cookie is not supplied.
> >> >> Remember, you have to call LogonUser first to get the cookie. You may
> >> >> find my WinForm sample useful to find out how to maintain and send
> >> >> the
> >> >> cookie from a non-web client.
> >> >>
> >> >> http://prologika.com/blog/archive/2004/08/27/169.aspx
> >> >>
> >> >>
> >> >> I am trying to implement the role-based piece of the security
> >> >> extension
> >> >> in
> >> >> a web farm environment. I think that I am having my issues because of
> >> >> the
> >> >> use of "HttpContext.Current.Cache" -- would this be an issue in a web
> >> >> farm?
> >> >> If so, do you have any alternatives other than to not cache the roles?
> >> >>
> >> >> Thanks!
> >> >
> >> >
> >>
> >>
> >>
>
>

Saturday, February 25, 2012

articles on sql 2005

Articles in more than one Category - How to organize tables?

articles about data access using System.Data.SqlClient namespace?

Article: Database Mirroring Not Ready for Production When SQL Server 2005 Ships

article row filter - 2 parameters

article request

article request

article request

article or some good reasons to kick devs out of production

article or some good reasons to kick devs out of production

article or some good reasons to kick devs out of production

article on Windows 2003 + sql

article on Windows 2003 + sql

article on Windows 2003 + sql

Article on when to use Stored Procs?

article on the optimiser generating a query plan

Article on Speeding up your SQL Server Development with easy to use tools

Article on RS Forms Authentication - Part II

sql nulls slow

Blog Archive

About Me

About Me

Followers

Blog Archive