Monday, March 19, 2012
Detailed information on individual security parameters
(on Security) or find the subject parameters elsewhere?
Hello,
Can you please explain in more detail what you looking for? Active Directory
Schema References contains all the default security descriptors applied to
each object class and attribute within Active Directory.
Search googel for "Active Directory Schema References "
Regards
Christoffer Andersson
Microsoft MVP - Directory Services
No email replies please - reply in the newsgroup
http://www.chrisse.se - Active Directory Resources
"SRVMAINT00" <apherson@.lycos.com> wrote in message
news:cgagf.63$SA4.4791@.news.uswest.net...
> Is there a location to either download the Windows 2000 Resource Kit Books
> (on Security) or find the subject parameters elsewhere?
>
>
|||"SRVMAINT00" <apherson@.lycos.com> wrote in message
news:cgagf.63$SA4.4791@.news.uswest.net...
> Is there a location to either download the Windows 2000 Resource Kit Books
> (on Security) or find the subject parameters elsewhere?
I would start with the Windows 2000 Security Guide and other documents at
www.microsoft.com/technet/security and also there is a lot of good
information for Windows 2000 at www.nsa.gov/snac
Detailed information on individual security parameters
(on Security) or find the subject parameters elsewhere?Hello,
Can you please explain in more detail what you looking for? Active Directory
Schema References contains all the default security descriptors applied to
each object class and attribute within Active Directory.
Search googel for "Active Directory Schema References "
Regards
Christoffer Andersson
Microsoft MVP - Directory Services
No email replies please - reply in the newsgroup
---
http://www.chrisse.se - Active Directory Resources
"SRVMAINT00" <apherson@.lycos.com> wrote in message
news:cgagf.63$SA4.4791@.news.uswest.net...
> Is there a location to either download the Windows 2000 Resource Kit Books
> (on Security) or find the subject parameters elsewhere?
>
>|||"SRVMAINT00" <apherson@.lycos.com> wrote in message
news:cgagf.63$SA4.4791@.news.uswest.net...
> Is there a location to either download the Windows 2000 Resource Kit Books
> (on Security) or find the subject parameters elsewhere?
I would start with the Windows 2000 Security Guide and other documents at
www.microsoft.com/technet/security and also there is a lot of good
information for Windows 2000 at www.nsa.gov/snac
Detailed information on individual security parameters
(on Security) or find the subject parameters elsewhere?Hello,
Can you please explain in more detail what you looking for? Active Directory
Schema References contains all the default security descriptors applied to
each object class and attribute within Active Directory.
Search googel for "Active Directory Schema References "
--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services
No email replies please - reply in the newsgroup
---
http://www.chrisse.se - Active Directory Resources
"SRVMAINT00" <apherson@.lycos.com> wrote in message
news:cgagf.63$SA4.4791@.news.uswest.net...
> Is there a location to either download the Windows 2000 Resource Kit Books
> (on Security) or find the subject parameters elsewhere?
>
>|||"SRVMAINT00" <apherson@.lycos.com> wrote in message
news:cgagf.63$SA4.4791@.news.uswest.net...
> Is there a location to either download the Windows 2000 Resource Kit Books
> (on Security) or find the subject parameters elsewhere?
I would start with the Windows 2000 Security Guide and other documents at
www.microsoft.com/technet/security and also there is a lot of good
information for Windows 2000 at www.nsa.gov/snac
Wednesday, March 7, 2012
Desperatly Need Help with MSDE installation and Config
Hi all, I know read all the posts already up on this subject... Hear me out.
Can anyone give an easy to understand, and I mean easy method for installing MSDE and configuring it so that I can connect to my server using Visual Studio.NET C#. I am having no end of troubles and I don't really understand why. I can log into osql using
osql -S BIGJ -E
that gets me to
1>
No problems so far
but when I try to connect using
SqlConnection("Server=BIGJ;DataBase=registeredUsers;Integrated Security=SSPI");
I am having no luck and I don't really understand why
Here is the stack trace
[SqlException: Login failed for user 'BIGJ\ASPNET'.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction)
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction)
System.Data.SqlClient.SqlConnection.Open()
ADOAccess.WebForm1.Button1_Click(Object sender, EventArgs e) in c:\inetpub\wwwroot\adoaccess\webform1.aspx.cs:52
System.Web.UI.WebControls.Button.OnClick(EventArgs e)
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
System.Web.UI.Page.ProcessRequestMain()
I think I am not understanding the fundamentals of SQL server or something so if anyone can help or point me to a good tutorial that will help me not only solve my problem but also understand what is going onas well.
Thanks everyone
Hi
You must add the user "MACHINENAME\ASPNET" in your case "BIGJ\ASPNET" to every db you run in your PC (localhost), that way .net can log on the db.
To do that (and much more) you can use this free tool:
http://forums.asp.net/631069/ShowPost.aspx
Regards
|||Thanks for the tip, I have SqlWDA installed but when I try and login it just hangs, I try using Windows integrated option and the SQL Login Option no luck just a frozen webpage.
Can you explain this, when I make a SqlConnection using Visual Studio dialog and press tesst connection it passes, if I copy that connection string into code I get the error I explained above? I'm really stuck
|||/* Give ASPNET User login rights to the server database */
if not exists (select * from master.dbo.syslogins where loginname = N'MACHINE_NAME\ASPNET')
exec sp_grantlogin N'MACHINE_NAME\ASPNET'
exec sp_defaultdb N'MACHINE_NAME\ASPNET', N'DataBase'
exec sp_defaultlanguage N'MACHINE_NAME\ASPNET', N'us_english'
GO
/* Give ASPNET User Access to database */
use [DataBase]
GO
if not exists (select * from dbo.sysusers where name = N'ASPNET' and uid < 16382)
EXEC sp_grantdbaccess N'MACHINE_NAME\ASPNET', N'ASPNET'
GO
/* Regards */
Friday, February 24, 2012
Design type question
Out of curosity I am asking this design type question because I am curious as to what thoughts you fine folks have on the subject matter.
I have seen many instances of a databse design where there are detail records that have a dollar value associated with them such as an invoice table which holds invoice records. I have noticed that no where is a total of the invoices stored, causing SQL to have to run through the records each time a total is needed.
In days gone by prior to SQL, data structures would be such that a total accumulator field in a data file somewhere would be updated as invoices were processed so that the system would not have to run through the individual records to derive the total of them.
I am familiar with normalization in terms of SQL as I have worked with SQL for years and of course I have work with non-SQL technologies before SQL came onto the scene. What I am curious to know is that is it such a bad thing in the SQL world to have something like an invoice total accumulator that constantly is updated as invoices are processed and queries can access this total accumulator directly rather than having to gather the individual invoice records and total them up first before presenting the total to the user?
If a total field is kept, you have the same data in two places. If you have the same data in two places, they can get out of sync.
Say I have three items at 5, 10 and 20 dollars and a total field of 35 dollars.
Sam, a student intern, edits an item and changes it from 5 to 7 dollars but doesn't recalculate the total field (because he's an intern and doesn't know).
Now the data is corrupt, the total field still has 35 dollars, but the real total is 37 dollars.
|||Actually I wasn't thinking in terms of a field that the user had access to thr the UI. Instead, a table for invoice id and invoice total, stored procedures would handle updating the invoice total in the table when the invoice itself from the invoice table was modified or new invoices added. Then when a total was needed for whatever reason the query could go right to the table and obtain the total rather than crunching the number.|||
It's a good question, but in the scenario you presented you are atucally causing much more harm than good. Here's why...
irasmith:
stored procedures would handle updating the invoice total in the table when the invoice itself from the invoice table was modified or new invoices added.
Now you are running that harsh code every time someone does an insert, or update... whereas if you just let SQL do the mathonly when it is being requested to be seen, it's much better. Also, as was mentioned above, it could get out of sync.
There is a place for storing, or "caching" the calculated value:
A friend of mine has just launched a HUGE project for the County, and in it there are certain bugeting calculations that take about 2 minutes to calculate. In this kind of invironment, caching (by storing the calculated value into a table) would not be so bad :P
That's my 2 cents :P
Peace,
|||I once worked on a project where once a day they ran a stored procedure that pulled data from another database and ran calculations on it, and then stored the information in a format that was easily read into reports, including precalculated totals. Of course the proc took about half an hour to run (don't ask) so there was no way you'd want to wait that long for a single invoice. As Nullable wrote, its pretty situational, but there are definately times you would want to 'cache' the data like this.|||Thanks to all who have posted to this thread. Naturally I am not one to run out and just do something out of the norm, however, as I work more in the design area I am finding that sometimes you have to weigh things and accept a trade off in order to accomplish the main goal. It is good to know others have had similar type issues arise before and while never an easy choice we just have to look at the specific situation and go from there.