Showing posts with label instance. Show all posts
Showing posts with label instance. Show all posts

Friday, March 30, 2012

I forgot my SA password for my instance of SQL 2000

Hi all,

I have SQL 2000 and I forgot my SA password and cannot login as administrator using windows authentication.

Is there any way to reset SA password?

"Mixed Mode" authentication is enabled.

If I change authentication mode in register to Windows only and then after restarting SQL change it back to Mixed, will it reset SA password to "null"?

Thanks in advance.

If you log onto the machine with the Database server installed and use the local administrator account or a network administrator account you should be able to reset the password.

|||Just in addition to Glenns post and your qustion: It won′t reset the password to null with changing the authentication type back and forth. If you don′t have any GUI to administer your passwords you can use the procedure sp_password passing in a NULL for the old password parameter, as you don′t need the old if you are logged on as a user with sysadmin / securityadmin rights.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||As I said before I can't login even with local Administrator. I don't know what is going on. It is so weird.

I forgot my SA password for my instance of SQL 2000

Hi all,

I have SQL 2000 and I forgot my SA password and cannot login as administrator using windows authentication.

Is there any way to reset SA password?

"Mixed Mode" authentication is enabled.

If I change authentication mode in register to Windows only and then after restarting SQL change it back to Mixed, will it reset SA password to "null"?

Thanks in advance.

If you log onto the machine with the Database server installed and use the local administrator account or a network administrator account you should be able to reset the password.

|||Just in addition to Glenns post and your qustion: It won′t reset the password to null with changing the authentication type back and forth. If you don′t have any GUI to administer your passwords you can use the procedure sp_password passing in a NULL for the old password parameter, as you don′t need the old if you are logged on as a user with sysadmin / securityadmin rights.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||As I said before I can't login even with local Administrator. I don't know what is going on. It is so weird.|||

Try

sp_password NULL,NULL,'sa'

Assuming you never created password at the first place. parameter 1 is Old password, parameters 2 is new password, parameter 3 is user.

Monday, March 26, 2012

I changed my windows password and now I cannot connect to SQL Server on my development mac

I changed the login password on my computer today, and now I cannot connect to the SQL Server instance I have on that same machine. I am using Windows Authentication.

I would think that, if I can log on to my computer, I would be able to connect to the database, since I have been "authenticated" by windows but, that does not appear to be the case.

Can anyone offer any advice?


Thanks in advance for any help you can provide.

When i doubt, restartWink

|||

I figured it out.

If anyone is interested...

I had to manually go to Administrative Tools > Services and choose (double-click) SQL Server (MSSQLSERVER). Then go to the Log On tab and change the password there. I did the same for SQL Server Agent (MSSQLSERVER). I haven't done any of the other SQL Server - related services on my machine. I will do those as needed, I guess, cause I am not using them yet.

I hope this helps someone.

|||

Ah, you're using your Windows login to run the SQL Server service. Generally not a good idea on a server, for the reason you found, but it is probably okay on a development machine.

Glad you figured it out!

Don

|||

Ahh...Thats the start up account. So your SQL Server is set up to start as a "Local Account". Generally its a good practice to use a Windows account that is not part of windows admnistrator group. Check out books on line for more info about SQL Server agent and the security model.

sql

I can't upgrade MSDE sp2 to sp3a

I am trying to upgrade an instance of MSDE on my XP computer using
setup /upgradesp sqlrun SECURITYMODE=SQL UPGRADEUSER=AnAdminLogin
UPGRADEPWD=AdminPassword
It runs for a while and then looks like it rolls back the installation. I
check the event viewer and I see an entry that states
"Product: Microsoft SQL Server Desktop Engine -- Configuration failed.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp."
But when I look further at the other entries I can see nothing that would
indicate why it failed.
I only have one instance of MSDE on my computer and this is the results of
my @.@.version before the upgrade
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1
(Build 2600: Service Pack 2)
I had checked the registry as per a MS article and it looks like it was
isntalled via sqlrun01.msi
Does anybody have any thoughts?
Thanks
Richard
hi Richard,
"Richard Speiss" <rspeiss@.mtxinc.com> ha scritto nel messaggio
news:%23WD%23x$TiEHA.1276@.TK2MSFTNGP09.phx.gbl...
> I am trying to upgrade an instance of MSDE on my XP computer using
> setup /upgradesp sqlrun SECURITYMODE=SQL UPGRADEUSER=AnAdminLogin
> UPGRADEPWD=AdminPassword
> It runs for a while and then looks like it rolls back the installation. I
> check the event viewer and I see an entry that states
> "Product: Microsoft SQL Server Desktop Engine -- Configuration failed.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp."
> But when I look further at the other entries I can see nothing that would
> indicate why it failed.
> I only have one instance of MSDE on my computer and this is the results of
> my @.@.version before the upgrade
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.1
> (Build 2600: Service Pack 2)
> I had checked the registry as per a MS article and it looks like it was
> isntalled via sqlrun01.msi
> Does anybody have any thoughts?
please add the
/L*v "c:\msdesp3.log"
command line parameter, in order to full log the installation to a (about)
2mb log txt file where you can search for
Return Value 3 in order to toubleshoot your upgrade
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql

Wednesday, March 21, 2012

i can't connect with the MSDE instance from another computer

I've installed a MSDE in one computer and i can access the
data without problems from the same computer , but if i
try to connect to the MSDE from another computer in the
same network , the instance doesn't appear. I tried from
almost 3 computers but i can't connect.
What i'm doing wrong?
Jorge,
If you installed the latest version the network protocols are probably
disabled (the default setting). Use svrnetcn.exe in the Binn folder under
your sql server directory to enable TCP/IP and things should work again. If
the machine with MSDE has a firewall make sure that the appropriate ports
can pass through the firewall (normally 1433). Use Properties on the
enabled TCP protocol to see the port used.
Ron Allen
"Jorge Lozano" <j.lozano@.initron20.com> wrote in message
news:07f001c49a51$94f2b8e0$a601280a@.phx.gbl...
> I've installed a MSDE in one computer and i can access the
> data without problems from the same computer , but if i
> try to connect to the MSDE from another computer in the
> same network , the instance doesn't appear. I tried from
> almost 3 computers but i can't connect.
> What i'm doing wrong?

Monday, March 19, 2012

I cannot get the SQL server compnent to install

I have tried to get the server component to install (SQL server instance) and it will not - what should I do?

What operating system and how many megs of ram?|||I am using XP Pro - and SQL Server 2005 Enterprise Edition

thank you for replying -
|||

You cannot install Enterprise on XP but you can install the developer which is like the Enterprise without deployment restrictions. Hope this helps.

http://www.microsoft.com/sql/prodinfo/sysreqs/default.mspx

Wednesday, March 7, 2012

i acn't login to a sql server with Database Engine Tuning Advisor

I'm trying to connect an instance (sql2005 standard edition) with the Database Engine Tuning Advisor (DETA), but it always fails.
I get this message:
"Failed to open a new connection.Failed to initialize MSDB database for tuning
(exit code: -1073741819).(DTAClient)"

The msdb database is exist on this server. What can i do?I compared the msdb database to an another db (where this feature is works) and I found some missing objects:
DTA% tables(22) and sp_DTA% store procedures(63)

I don't remember any option where I can set this objects (exist or not) and I didn't see any error when I installed this server.
?|||

This is most likely a security issue. The login account you are using from the tuning advisor doesn't have sufficient privileges to MSDB. The account you use for database tuning should have read/write access to msdb, because the DTA stores session information there (see BOL topic Considerations for Using Database Engine Tuning Advisor).

Sunday, February 19, 2012

Hyde database features ...

My application setup program installs a MSDE2K instance on the user machine,
then attaches the application database (previously prepared with sa access
on the development machine), adds server logins and db users, sets
permissions etc. Everything goes fine, but I would like to hide my database
design, preventing the sysadmin of the target machine (NT) to view its
tables structure and relationships. How can I make my database protected 'by
itself' ?
hi Alessandro,
"Alessandro T" <alessandroteglia@.tin.it> ha scritto nel messaggio
news:ut2uAGWIEHA.3988@.tk2msftngp13.phx.gbl...
> My application setup program installs a MSDE2K instance on the user
machine,
> then attaches the application database (previously prepared with sa access
> on the development machine), adds server logins and db users, sets
> permissions etc. Everything goes fine, but I would like to hide my
database
> design, preventing the sysadmin of the target machine (NT) to view its
> tables structure and relationships. How can I make my database protected
'by
> itself' ?
>
it is not possible to prevent a sysadmin member to access your data and/or
metaschema ...
to prevent access to data area you have to resort to crypt solutions like
http://www.activecrypt.com/index.htm or your own algorithms, while for
schema hiding, you are only provided with the WITH ENCRYPTION option and for
stored procedure, views and user defined functions only...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply