﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Discuss Content Posted by Steve Jones / Article Discussions / Article Discussions by Author  / Beginning SQL Server - Logins and Users / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Sun, 19 May 2013 12:28:14 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Beginning SQL Server - Logins and Users</title><link>http://www.sqlservercentral.com/Forums/Topic129731-32-1.aspx</link><description>Steve, excellent post on logins/users! Do you have an updated 2005/2008 version of this? Any help would be greatly appreciated. Thanks!Sharma</description><pubDate>Thu, 04 Feb 2010 19:44:46 GMT</pubDate><dc:creator>SQLSharma</dc:creator></item><item><title>RE: Beginning SQL Server - Logins and Users</title><link>http://www.sqlservercentral.com/Forums/Topic129731-32-1.aspx</link><description>Always good to review the basics.  I noticed that the .\ usage in figure 7 was no different than if I click the ... button without it.  Am I missing something?I learned something about security recently that surprised me.  The situation is like this.  I have a member who is part of a server group.  That group has permissions to a database.  The specified user cannot connect directly to the database using Query Analyzer.  I was a bit surprised, shows an advantage to SQL logins as opposed to Windows login.  It's also possible that I didn't do a valid attempt and my result is meaningless.Also recently I found a use for Deny.  I have a reporting database where we want to strictly limit user's access to data.   All of these users are in a server group.  The ERP system has a set of views provided by the vendor.  So we created a second database, created a 'select * from livedb..' set of queries by the same name as the vendor queries and gave the group select permissions to said views.In the production DB, we denied them select on sysobjects and no select permissions on the vendor views.  Apparently by denying the select on sysobjects, you also keep them from running sp_helptext on the views, so they can't see what the code is behind the vendor views.</description><pubDate>Fri, 03 Aug 2007 11:18:00 GMT</pubDate><dc:creator>Wayne West</dc:creator></item><item><title>RE: Beginning SQL Server - Logins and Users</title><link>http://www.sqlservercentral.com/Forums/Topic129731-32-1.aspx</link><description>&lt;P&gt;Helow! The article is very good and clear, but i need... how i can to do this with commands T-SQL...?? Help me!! thank you!!&lt;/P&gt;&lt;P&gt; &lt;/P&gt;</description><pubDate>Thu, 13 Jan 2005 09:36:00 GMT</pubDate><dc:creator>Burela Miguel Angel</dc:creator></item><item><title>Beginning SQL Server - Logins and Users</title><link>http://www.sqlservercentral.com/Forums/Topic129731-32-1.aspx</link><description>Comments posted to this topic are about the content posted at &lt;A HREF=http://www.sqlservercentral.com/columnists/sjones/beginningsqlserverloginsandusers.asp&gt;http://www.sqlservercentral.com/columnists/</description><pubDate>Mon, 02 Aug 2004 14:59:00 GMT</pubDate><dc:creator>Steve Jones - SSC Editor</dc:creator></item></channel></rss>