Deprecated: Function set_magic_quotes_runtime() is deprecated in /usr/local/apache/sites/mcse.ms/htdocs/362/includes/class_core.php on line 1505

Call Stack:
    0.0001     326800   1. {main}() /usr/local/apache/sites/mcse.ms/htdocs/362/archive/index.php:0
    0.0003     327652   2. require_once('/usr/local/apache/sites/mcse.ms/htdocs/362/archive/global.php') /usr/local/apache/sites/mcse.ms/htdocs/362/archive/index.php:25
    0.0004     328940   3. require_once('/usr/local/apache/sites/mcse.ms/htdocs/362/includes/init.php') /usr/local/apache/sites/mcse.ms/htdocs/362/archive/global.php:20
    0.0013     403244   4. vB_Registry->vB_Registry() /usr/local/apache/sites/mcse.ms/htdocs/362/includes/init.php:43
    0.0014     403900   5. vB_Input_Cleaner->vB_Input_Cleaner() /usr/local/apache/sites/mcse.ms/htdocs/362/includes/class_core.php:2337

<br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/archive/global.php</strong> on line <strong>26</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3113</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html dir="ltr" lang="en">
<head>
	<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
	<meta name="keywords" content="Beginner security questions, vbulletin,forum,bbs,discussion,jelsoft,bulletin board" />
	<meta name="description" content="[Archive] Beginner security questions SQL Server Security" />
	
	<title>Beginner security questions [Archive]  - MCSE</title>
	<link rel="stylesheet" type="text/css" href="http://www.mcse.ms/archive/archive.css" />
</head>
<body>
<div class="pagebody">
<div class="archiver"><script type="text/javascript"><!--
google_ad_client = "pub-6314654110945947";
google_ad_width = 468;
google_ad_height = 15;
google_ad_format = "468x15_0ads_al";
google_ad_channel = "9315981861";
google_color_border = "2B4271";
google_color_bg = "FFFFFF";
google_color_link = "000080";
google_color_url = "008000";
google_color_text = "000000";
//--></script>
<script type="text/javascript"
  src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>


</div>
<div id="navbar"><a href="./">MCSE</a> &gt; <a href="f-16.html">Microsoft software reviews</a> &gt; <a href="f-32.html">Microsoft SQL server reviews</a> &gt; <a href="f-97.html">SQL Server Security</a> &gt; Beginner security questions</div>
<hr />
<div class="pda"><a href="?pda=1" rel="nofollow">PDA</a></div>
<p class="largefont">View Full Version : <a href="http://www.mcse.ms/showthread.php?t=559014">Beginner security questions</a></p>
<hr />
<div class="ggat">
<script type="text/javascript"><!--
	google_ad_client = "pub-6314654110945947";
	google_ad_width = 728;
	google_ad_height = 90;
	google_ad_format = "728x90_as";
	google_ad_channel ="9315981861";
	google_color_border = "FFFFFF";
	google_color_bg = "FFFFFF";
	google_color_link = "0000FF";
	google_color_url = "000080";
	google_color_text = "000000";
	//--></script>
	<script type="text/javascript"
	  src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>
</div>
<div class="post"><div class="posttop"><div class="username">Jack Wachtler</div><div class="date">04-11-04, 09:50 PM</div></div><div class="posttext"><div class="ggap">something</div>Thanks in advance for your patience with my beginner questions.<br />
<br />
I have a SQL Server instance setup on my XP desktop (the 120 day Evaluation Edition - V8.00.194). When I installed it I setup the instance with &quot;Windows Only&quot; authentication.<br />
<br />
I have myself and my wife with XP user accounts and also have a guest user account active. I created a database for practice, and would like allow either my wife's account or the guest account to login and access the one practice database, with select pri<br />
viledge's only on tables. Ideally from these &quot;user&quot; XP accounts, I would like to allow access to my practice database only through the Query Analyzer Window. I don't want to allow these accounts to see other databases or system tables. I don't want them t<br />
o be able to stratup Enterprise Manager or any tool other than Query Analyzer for the one database.<br />
<br />
What are the steps I need to follow to create permissions? After I do these steps, I want to log in through the guest account and see that my security setup works.<br />
<br />
I have read the chapters in my textbook on security, but still don't really get it. I guess I need a simpler example that I can practice for myself.<br />
<br />
Your help in teaching a newbie is greatly appreciated.</div></div><hr />


<div class="post"><div class="posttop"><div class="username">Mary Chipman</div><div class="date">04-11-04, 09:50 PM</div></div><div class="posttext"><div class="ggap">something</div>If your goal is to learn how security works by playing with it, the<br />
quickest way is to enable mixed-mode authentication. Then you can<br />
create SQL logins (which are unavailable in Windows Only mode) and<br />
assign them permissions, which you can then test using the Query<br />
Analyzer, which lets you open multiple connections based on different<br />
logins. Once you've tested and debugged security using SQL logins to<br />
mimic your eventual Windows logins, you can delete them and assign<br />
Windows logins to the roles you've created and set your security mode<br />
back to Windows only for production. Not sure which textbook you are<br />
using, but this site has lots of useful resources:<br />
http://www.microsoft.com/sql/techinfo/administration/2000/security/default.asp<br />
<br />
--Mary<br />
<br />
On Tue, 30 Mar 2004 12:56:10 -0800, &quot;Jack Wachtler&quot;<br />
&lt;jack_wachtler@comcast.net&gt; wrote:<br />
<br />
&gt;Thanks in advance for your patience with my beginner questions.<br />
&gt;<br />
&gt;I have a SQL Server instance setup on my XP desktop (the 120 day Evaluation Edition - V8.00.194). When I installed it I setup the instance with &quot;Windows Only&quot; authentication.<br />
&gt;<br />
&gt;I have myself and my wife with XP user accounts and also have a guest user account active. I created a database for practice, and would like allow either my wife's account or the guest account to login and access the one practice database, with select pr<br />
iviledge's only on tables. Ideally from these &quot;user&quot; XP accounts, I would like to allow access to my practice database only through the Query Analyzer Window. I don't want to allow these accounts to see other databases or system tables. I don't want them<br />
to be able to stratup Enterprise Manager or any tool other than Query Analyzer for the one database.<br />
&gt;<br />
&gt;What are the steps I need to follow to create permissions? After I do these steps, I want to log in through the guest account and see that my security setup works.<br />
&gt;<br />
&gt;I have read the chapters in my textbook on security, but still don't really get it. I guess I need a simpler example that I can practice for myself.<br />
&gt;<br />
&gt;Your help in teaching a newbie is greatly appreciated.</div></div><hr />


<div class="post"><div class="posttop"><div class="username">Svein Terje Gaup</div><div class="date">04-12-04, 05:34 PM</div></div><div class="posttext"><div class="ggap">something</div>Since you've installed with &quot;Windows Only&quot; you may have a few steps to take<br />
before you can allow other users to access the database. Normally this<br />
option works if the SQL Server is part of a domain, which I presume your<br />
machines are not part of. You could try to create a user account on the SQL<br />
Server that has the same name as the user your wife is using on her XP, with<br />
the same password. This might work (I'm not sure).<br />
<br />
An other option is to change the security to &quot;Mixed mode&quot;, and create SQL<br />
Server accounts. You may be able to change the licensing by way of the &quot;SQL<br />
Server 2000 Licensing&quot; icon on the control panel. However the &quot;Mixed mode&quot;<br />
option may be grayed out. In that case you could do one of two things:<br />
1. Reinstall sql server in mixed mode (remember to back up your database<br />
first)<br />
OR<br />
2. You could do this (cut from another posting found on Google):<br />
Change the LoginMode value of the<br />
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\  MSSQLServer registry key<br />
(for default instance).<br />
1 = Windows Only<br />
2 = SQL Server and Windows<br />
<br />
--<br />
Sincerely<br />
Svein Terje Gaup<br />
<br />
&quot;Jack Wachtler&quot; &lt;jack_wachtler@comcast.net&gt; wrote in message<br />
news:01A128AE-2A11-4719-BB37-DC8B683D662A@microsoft.com...<br />
&gt; Thanks in advance for your patience with my beginner questions.<br />
&gt;<br />
&gt; I have a SQL Server instance setup on my XP desktop (the 120 day<br />
Evaluation Edition - V8.00.194). When I installed it I setup the instance<br />
with &quot;Windows Only&quot; authentication.<br />
&gt;<br />
&gt; I have myself and my wife with XP user accounts and also have a guest user<br />
account active. I created a database for practice, and would like allow<br />
either my wife's account or the guest account to login and access the one<br />
practice database, with select priviledge's only on tables. Ideally from<br />
these &quot;user&quot; XP accounts, I would like to allow access to my practice<br />
database only through the Query Analyzer Window. I don't want to allow these<br />
accounts to see other databases or system tables. I don't want them to be<br />
able to stratup Enterprise Manager or any tool other than Query Analyzer for<br />
the one database.<br />
&gt;<br />
&gt; What are the steps I need to follow to create permissions? After I do<br />
these steps, I want to log in through the guest account and see that my<br />
security setup works.<br />
&gt;<br />
&gt; I have read the chapters in my textbook on security, but still don't<br />
really get it. I guess I need a simpler example that I can practice for<br />
myself.<br />
&gt;<br />
&gt; Your help in teaching a newbie is greatly appreciated.</div></div><hr />

<div id="cbd">vBulletin v3.6.2, Copyright &copy;2000-2010, Jelsoft Enterprises Ltd.</div>
</div>
<SCRIPT language="javascript" src="http://examnotes.us.intellitxt.com/intellitxt/front.asp?IPID=917&MK=10&FG=0000FF&SN=g8,cbd"></SCRIPT>
</body>
</html>