Need to Change Developers Acct to Windows Authentication

I have my SQL 7.0 server set for Mixed security. I see now (finally)
the advantages of having windows authentication security for windows
groups.
I do most of my developing in Access Projects which require a login of
some type. I have been using my SQL login to develop with SQL and
then when I give it to the user, I set the project to use Windows
authentication. I want to be able to have Windows authentication on
my domain account but the user name for my windows account is the same
as my SQL account and it won't let me change the existing account.
Now what happens is after I develop the product I have to have the
user login and go in and change to windows authentication. It won't
let me do it with my sql account.

I fear that if I delete my sql account and create a windows
authentication account all the views, sps, etc. that I have created
will still have the reference to the sql login and therefore not work.

Do I need to have a generic sql account for developing? One thought I
had was to create a new domain account so I can create that windows
login and at least get my most recent projects working like I want to?

Hope this makes sense to someone.
Thanks in advance for your time.
Sherry"sherkozmo" <skosmicki@.sfmc-gi.org> wrote in message
news:3ff08a65.0409280648.2d0c3d4f@.posting.google.c om...
>I have my SQL 7.0 server set for Mixed security. I see now (finally)
> the advantages of having windows authentication security for windows
> groups.
> I do most of my developing in Access Projects which require a login of
> some type. I have been using my SQL login to develop with SQL and
> then when I give it to the user, I set the project to use Windows
> authentication. I want to be able to have Windows authentication on
> my domain account but the user name for my windows account is the same
> as my SQL account and it won't let me change the existing account.
> Now what happens is after I develop the product I have to have the
> user login and go in and change to windows authentication. It won't
> let me do it with my sql account.

You might find this post from yesterday useful - it gives a short overview
of moving from SQL to Windows authentication:

http://groups.google.com/groups?hl=...s.prodi gy.com

One solution to your issue (if I understood correctly) is to connect as sa,
drop the SQL login, grant login to your Windows account, then logout and
connect with Windows authentication.

> I fear that if I delete my sql account and create a windows
> authentication account all the views, sps, etc. that I have created
> will still have the reference to the sql login and therefore not work.

If the objects are owned by dbo, then there should be no problem. If the
objects are owned by a SQL login, then you can always change the owner with
sp_changeobjectowner - the bext practice would be to use dbo for production
objects anyway.

> Do I need to have a generic sql account for developing? One thought I
> had was to create a new domain account so I can create that windows
> login and at least get my most recent projects working like I want to?

It is almost always best to avoid generic accounts - there's no way to know
who is really using it, so auditing and permissions are difficult to
implement properly. The best solution is probably roles eg. your Windows
account is in the db_owner role, but user accounts are in a role with more
limited permissions.

> Hope this makes sense to someone.
> Thanks in advance for your time.
> Sherry

You're welcome.

Simon

Need to change Authentication type of my first DB in SQL05

* I was able to configure and install the DB

* I accidentally selected Windows Authentication

Now it won't let me login and keeps giving me an error.

Question: how do i change the authentication type without getting into the db? is there something I'm missing?

The authentication method is Server level, not database level. (Are you able to access the Server -but not a specific database?)

IF so, using SSMS, in the Object Explorer pane, right-click on the Server, and then select the [Security] tab. Change the authentication method there.

If you are not able to access the Server using SSMS, it may be just as quick for you to re-install (or) let us know so we can walk you through the process.

|||Sql service is necessary after changing the authentication mode on server level. Hence do a restart after changing the authentication mode.

Need official MS response - rename/remove 'sa' account?

I need to get an official MS response on whether it is possible to rename or
remove the 'sa' account when using Mixed Mode authentication on SQL Server
2000. This is to satisfy some audit points for our company.
Thanks.
-Pete SchottYou don't generally get official MS responses on a newsgroup. You are going
to have to contact Microsoft directly for that.
The unofficial answer is that neither is possible.
--
Hal Berenson, SQL Server MVP
True Mountain Group LLC
"Peter A. Schott" <pschott@.drivefinancial.com> wrote in message
news:r3o0iv4fecv9iicenjruhcnecp05fhbcbc@.4ax.com...
> I need to get an official MS response on whether it is possible to rename
or
> remove the 'sa' account when using Mixed Mode authentication on SQL Server
> 2000. This is to satisfy some audit points for our company.
> Thanks.
> -Pete Schott|||On Thu, 24 Jul 2003 17:07:43 -0600, "Hal Berenson"
<haroldb@.truemountainconsulting.com> wrote:
>The unofficial answer is that neither is possible.
Hal, wasn't doing both a standard security suggestion back in 6.5
days?
I haven't engaged in this recently, but assumed it was still possible
and even advisable.
Joshua Stern|||Hello Pete,
Thank you for your posting. I did some research on the "sa" login removal.
If you notice the option to remove the "sa" login is not provided in
Enterprise Manager since you cannot remove sa login. If you refer to Books
Online , under sp_droplogin ( the command used to drop a login), the
following caveats exist :
Remarks
A login mapped to an existing user in any database cannot be removed. The
user must be removed first by using sp_dropuser. Additionally, these logins
cannot be removed:
The system administrator (sa) login.
A login that owns an existing database.
A login that owns jobs in the msdb database.
A login that is currently in use and connected to SQL Server.
Therefore, by design "sa" cannot be removed. However. please note that by
using Windows Nt Authentication, we can bypass the use of "sa" . The SQL
server will then authenticate Windows Nt logins only. Due to this reason
and the fact that as per SQL 2000 Books Online, sa has been included for
backward compatibility purposes, you may want to carefully examine the use
of this login for application development purposes.
If you have further questions on the issue, please feel free to post back.
Thanks & Regards,
Peter Yang
MCSE2000, MCSA, MCDBA
Microsoft Partner Online Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
| From: Peter A. Schott <pschott@.drivefinancial.com>
| Subject: Need official MS response - rename/remove 'sa' account?
| Date: Thu, 24 Jul 2003 17:42:00 -0500
| Message-ID: <r3o0iv4fecv9iicenjruhcnecp05fhbcbc@.4ax.com>
| X-Newsreader: Forte Agent 1.93/32.576 English (American)
| MIME-Version: 1.0
| Content-Type: text/plain; charset=us-ascii
| Content-Transfer-Encoding: 7bit
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: drivefinancial.com 65.105.152.62
| Lines: 1
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.server:297733
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| I need to get an official MS response on whether it is possible to rename
or
| remove the 'sa' account when using Mixed Mode authentication on SQL Server
| 2000. This is to satisfy some audit points for our company.
|
| Thanks.
|
| -Pete Schott
||||The 'sa' login renaming feature is also not provided.
Simply set a strong password for 'sa', that cannot be guessed by dictionary
based attacks.
Switch to Windows authentication, so that 'sa' is basically useless.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
What hardware is your SQL Server running on?
http://vyaskn.tripod.com/poll.htm
"Peter A. Schott" <pschott@.drivefinancial.com> wrote in message
news:npf2ivgmmlg9ca2qntpfsdrms93269lppf@.4ax.com...
Peter,
One more question - is there anything about renaming 'sa'? If it's
possible and supported, I will have to do that. If it's not possible or
supported, I will need to provide some formal document about that.
While I'm sure it's possible, I'm pretty sure that it's not supported, but
need to know for sure.
If you don't know, can you direct me to the appropriate contact who can give
me a definite answer?
Thanks.
-Pete Schott
petery@.online.microsoft.com (Peter Yang [MSFT]) wrote:
> Hello Pete,
> Thank you for your posting. I did some research on the "sa" login removal.
> If you notice the option to remove the "sa" login is not provided in
> Enterprise Manager since you cannot remove sa login. If you refer to Books
> Online , under sp_droplogin ( the command used to drop a login), the
> following caveats exist :
> Remarks
> A login mapped to an existing user in any database cannot be removed. The
> user must be removed first by using sp_dropuser. Additionally, these
logins
> cannot be removed:
> The system administrator (sa) login.
> A login that owns an existing database.
> A login that owns jobs in the msdb database.
> A login that is currently in use and connected to SQL Server.
> Therefore, by design "sa" cannot be removed. However. please note that by
> using Windows Nt Authentication, we can bypass the use of "sa" . The SQL
> server will then authenticate Windows Nt logins only. Due to this reason
> and the fact that as per SQL 2000 Books Online, sa has been included for
> backward compatibility purposes, you may want to carefully examine the use
> of this login for application development purposes.
> If you have further questions on the issue, please feel free to post back.
> Thanks & Regards,
> Peter Yang
> MCSE2000, MCSA, MCDBA
> Microsoft Partner Online Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> --
> | From: Peter A. Schott <pschott@.drivefinancial.com>
> | Subject: Need official MS response - rename/remove 'sa' account?
> | Date: Thu, 24 Jul 2003 17:42:00 -0500
> | Message-ID: <r3o0iv4fecv9iicenjruhcnecp05fhbcbc@.4ax.com>
> | X-Newsreader: Forte Agent 1.93/32.576 English (American)
> | MIME-Version: 1.0
> | Content-Type: text/plain; charset=us-ascii
> | Content-Transfer-Encoding: 7bit
> | Newsgroups: microsoft.public.sqlserver.server
> | NNTP-Posting-Host: drivefinancial.com 65.105.152.62
> | Lines: 1
> | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
> | Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.server:297733
> | X-Tomcat-NG: microsoft.public.sqlserver.server
> |
> | I need to get an official MS response on whether it is possible to
rename
> or
> | remove the 'sa' account when using Mixed Mode authentication on SQL
Server
> | 2000. This is to satisfy some audit points for our company.
> |
> | Thanks.
> |
> | -Pete Schott
> |

Need help!

I really just do not understand this and it is really frustrating me... I
made a custom authentication/authorization extension that uses forms
authentication... it works fine on my local system (32bit windows xp pro sp2
with SQL 2005 Dev SP2)... So I installed it onto our development test server
running SQL 2005 Dev edition SP2 (32bit windows server 2003) works great!
figure ok its working! now I go to our master setup, which is like this
Active/Passive failover cluster with shared storage on a SAN... 2 node
cluster... both running windows server 2003 64bit! SQL Server is clustered,
but we dont care much about reporting services being fail over because they
fail so infrequently.. so I do all the same stuff I do to install it on the
32bit server... now this is what happends
I open up http://sqlvirtualhost/Reports (sqlvirtualhost is the virtual
cluster name we gave the sql server instance) it goes to the report server
logon screen, I login, that works fine... I get a list of reports, ok great!
seems to be working! I click on a report... boom problem... gives me a .net
assembly name that has Microsoft.ReportingService.xxxxx in (xxxx changes
sometimes usually Modeling or Design seems like?) anyways it says Access
Denied is the error and thats it! I cant figure out what is denied access or
what is causing it... this same thing with the same config works great on
the two 32bit systems! the assembly is compiled for "AutoCPU" to let .NET
framework auto compile it to 32 or 64bit on demand... im ripping out my hair
here, can anyone help me or give me some direction on what to do or look
for? THANKS A LOT!I added the computer in the domain to the security list that sharepoint
services is on and now the message changed to this "HTTP/1.1 404 Connection:
close Date: Wed, 28 Feb 2007 21:42:58 GMT Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 12.0.0.4518 "
"Smokey Grindel" <nospam@.nospam.com> wrote in message
news:uuYkGzrWHHA.488@.TK2MSFTNGP06.phx.gbl...
>I really just do not understand this and it is really frustrating me... I
>made a custom authentication/authorization extension that uses forms
>authentication... it works fine on my local system (32bit windows xp pro
>sp2 with SQL 2005 Dev SP2)... So I installed it onto our development test
>server running SQL 2005 Dev edition SP2 (32bit windows server 2003) works
>great! figure ok its working! now I go to our master setup, which is like
>this
> Active/Passive failover cluster with shared storage on a SAN... 2 node
> cluster... both running windows server 2003 64bit! SQL Server is
> clustered, but we dont care much about reporting services being fail over
> because they fail so infrequently.. so I do all the same stuff I do to
> install it on the 32bit server... now this is what happends
>
> I open up http://sqlvirtualhost/Reports (sqlvirtualhost is the virtual
> cluster name we gave the sql server instance) it goes to the report server
> logon screen, I login, that works fine... I get a list of reports, ok
> great! seems to be working! I click on a report... boom problem... gives
> me a .net assembly name that has Microsoft.ReportingService.xxxxx in
> (xxxx changes sometimes usually Modeling or Design seems like?) anyways it
> says Access Denied is the error and thats it! I cant figure out what is
> denied access or what is causing it... this same thing with the same
> config works great on the two 32bit systems! the assembly is compiled for
> "AutoCPU" to let .NET framework auto compile it to 32 or 64bit on
> demand... im ripping out my hair here, can anyone help me or give me some
> direction on what to do or look for? THANKS A LOT!
>|||you have this error when you have reporting service with sharepoint services
on?
did you have this issue still? i have the same issue and i solved it by
adding the report server url in sharepoint server exlude list..
- Bava
"Smokey Grindel" wrote:
> I added the computer in the domain to the security list that sharepoint
> services is on and now the message changed to this "HTTP/1.1 404 Connection:
> close Date: Wed, 28 Feb 2007 21:42:58 GMT Server: Microsoft-IIS/6.0
> X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 12.0.0.4518 "
>
> "Smokey Grindel" <nospam@.nospam.com> wrote in message
> news:uuYkGzrWHHA.488@.TK2MSFTNGP06.phx.gbl...
> >I really just do not understand this and it is really frustrating me... I
> >made a custom authentication/authorization extension that uses forms
> >authentication... it works fine on my local system (32bit windows xp pro
> >sp2 with SQL 2005 Dev SP2)... So I installed it onto our development test
> >server running SQL 2005 Dev edition SP2 (32bit windows server 2003) works
> >great! figure ok its working! now I go to our master setup, which is like
> >this
> >
> > Active/Passive failover cluster with shared storage on a SAN... 2 node
> > cluster... both running windows server 2003 64bit! SQL Server is
> > clustered, but we dont care much about reporting services being fail over
> > because they fail so infrequently.. so I do all the same stuff I do to
> > install it on the 32bit server... now this is what happends
> >
> >
> > I open up http://sqlvirtualhost/Reports (sqlvirtualhost is the virtual
> > cluster name we gave the sql server instance) it goes to the report server
> > logon screen, I login, that works fine... I get a list of reports, ok
> > great! seems to be working! I click on a report... boom problem... gives
> > me a .net assembly name that has Microsoft.ReportingService.xxxxx in
> > (xxxx changes sometimes usually Modeling or Design seems like?) anyways it
> > says Access Denied is the error and thats it! I cant figure out what is
> > denied access or what is causing it... this same thing with the same
> > config works great on the two 32bit systems! the assembly is compiled for
> > "AutoCPU" to let .NET framework auto compile it to 32 or 64bit on
> > demand... im ripping out my hair here, can anyone help me or give me some
> > direction on what to do or look for? THANKS A LOT!
> >
>
>|||any update on this issue? please let me know how do you resolve the issue.
"Bava Mani" wrote:
> you have this error when you have reporting service with sharepoint services
> on?
> did you have this issue still? i have the same issue and i solved it by
> adding the report server url in sharepoint server exlude list..
> - Bava
> "Smokey Grindel" wrote:
> > I added the computer in the domain to the security list that sharepoint
> > services is on and now the message changed to this "HTTP/1.1 404 Connection:
> > close Date: Wed, 28 Feb 2007 21:42:58 GMT Server: Microsoft-IIS/6.0
> > X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 12.0.0.4518 "
> >
> >
> > "Smokey Grindel" <nospam@.nospam.com> wrote in message
> > news:uuYkGzrWHHA.488@.TK2MSFTNGP06.phx.gbl...
> > >I really just do not understand this and it is really frustrating me... I
> > >made a custom authentication/authorization extension that uses forms
> > >authentication... it works fine on my local system (32bit windows xp pro
> > >sp2 with SQL 2005 Dev SP2)... So I installed it onto our development test
> > >server running SQL 2005 Dev edition SP2 (32bit windows server 2003) works
> > >great! figure ok its working! now I go to our master setup, which is like
> > >this
> > >
> > > Active/Passive failover cluster with shared storage on a SAN... 2 node
> > > cluster... both running windows server 2003 64bit! SQL Server is
> > > clustered, but we dont care much about reporting services being fail over
> > > because they fail so infrequently.. so I do all the same stuff I do to
> > > install it on the 32bit server... now this is what happends
> > >
> > >
> > > I open up http://sqlvirtualhost/Reports (sqlvirtualhost is the virtual
> > > cluster name we gave the sql server instance) it goes to the report server
> > > logon screen, I login, that works fine... I get a list of reports, ok
> > > great! seems to be working! I click on a report... boom problem... gives
> > > me a .net assembly name that has Microsoft.ReportingService.xxxxx in
> > > (xxxx changes sometimes usually Modeling or Design seems like?) anyways it
> > > says Access Denied is the error and thats it! I cant figure out what is
> > > denied access or what is causing it... this same thing with the same
> > > config works great on the two 32bit systems! the assembly is compiled for
> > > "AutoCPU" to let .NET framework auto compile it to 32 or 64bit on
> > > demand... im ripping out my hair here, can anyone help me or give me some
> > > direction on what to do or look for? THANKS A LOT!
> > >
> >
> >
> >