Showing posts with label password. Show all posts
Showing posts with label password. Show all posts

Friday, March 30, 2012

MSDE SQL Connection String error

Hi;
Installed MSDE on computer by running:

c:setup INSTANCENAME="VSdotNET" SAPWD="PASSWORD" SECURITYMODE=SQL

REBOOTED AND sql SERVER iCON APPEARS on the lower desktop Icon bar, open it and it says:
Server: JOHN Servises: SQL Server Running \\JOHN - MSSQLServer

opened a command prompt at c: and
entered osql -S JOHN -U sa -P password
and got the 1> reply on the next line

I typed EXIT

I had downloaded two scripts that create Pubs and Northwind SQL databases. I put them in the C: folder

I Typed at c:osql -E -i instpubs.sql

It created the pubs SQL database for me

I Typed at c:osql -E -i instnwinds.sql

It created the nwinds SQL database for me

I closed the command prompt and
went to the Administrator Tools in the Control Panel
I selected Data OLEDB Selected ADD entered Pubs and used default values for Pubs to create a connection Tested it OK

Then went and ran Visual Studio Net 2003
Checked to see if the pubs and northwind SQL databases where present in the Server Explorer drop down window.
I seleced the connect to database Icon and in it's Data Link Properties
I entered JOHN for server name
pubs for selected database on the server
with Provider as MS OLEDB for SQL Service
the Icon changed to connected.

I entered this in the code for page_load


Dim MyDS As New DataSet
Dim ConnStr As String
Dim SQL As String
ConnStr = "server=(local)C:\Program Files\Microsoft SQL Server\MSSQL\Data;database=pubs;Trusted_Connection=yes"

SQL = "SELECT * FROM Titles " & _
"SELECT * FROM Publishers"
Dim MySqlConn As New SqlConnection(ConnStr)
Dim MySqlAdapter As New SqlDataAdapter(SQL, ConnStr)

'The SqlDataAdapter will automatically open and
'close the SqlConnection
MySqlAdapter.Fill(MyDS)


But I can not get this to work it errors out on line:

MySQLAdapter.Fill(myDS)

with: [SqlException (0x80131904): Unknown ProviderError Locating Server/Instance Specified ]
System.Data.ProviderBase.DbConnectionPool.GetConnection(Object owningObject) +317

I change ConnStr to this:


ConnStr = "server=(local)\data;database=pubs; uid=sa; Pwd=password" & _
"Trusted_Connection=true"

and get this error:
[SqlException (0x80131904): Shared Memory Provider: The system cannot find the file specified.
]
System.Data.ProviderBase.DbConnectionPool.GetConnection(Object owningObject) +317

I've tried so many combination with and without user and password, I just don't get it, spent three long days stuck here, can someone help me out.

Note:
C:\Program Files\Microsoft SQL Server\MSSQL\Data
Is the accual location on my machine that pubs database is located.

I can use the pubs SQL database in Web Matrix OK.
Thanks
pdqjohnny@.hotmail.comHi;
Well I went back to VS and used the Drag/Drop from the Server Explorer DataConnections window to get a SQL Connection on my form. I then looked at the properties and copied the connection property in created for me.

ConnStr = "workstation id=JOHN;packet size=4096;integrated security=SSPI;data source=JOHN;persist security info=False;initial catalog=pubs"

and then cut/replace my old Connstr shown above with it.

Now I get this ERROR:

SELECT permission denied on object 'titles', database 'pubs', owner 'dbo'.
SELECT permission denied on object 'publishers', database 'pubs', owner 'dbo'.

Can anybody help?
Thanks
John|||OK
I continued with my search and found someone mention this link for program called
Microsoft SQL Server Web Data Administrator (for MSDE or IIS)
http://asp.net/Projects/Cassini/Download/Default.aspx?tabindex=0&tabid=1

I downloaded and installed it then ran it.

I found that my Server=John\ASPNET was not assigned to the pubs database (I THINK)

so I Selected: IIS, Start, Windows Integated, server Roles
then I picked the top entry Sytem Administrators, there ar about 8 rows shown here
then to the far right in it's row was:
Add or Edit Logins
so I click on them I new window opened.
It showed Available Login: names in the left window where
"John\ASPNET and sa"
So I moved all of them to the right to the Assigned logins: window
and clicked Done.
I exited out of this program and went back to VS 2003 to my program mention above.
I changed the ConnStr to this:


ConnStr = "server=JOHN;database=pubs;uid=sa;" & _
"Trusted_Connection=true"

Ok it runs nowsql

Wednesday, March 28, 2012

MSDE sp3a install w/ no password

I was just wondering how I could install an instance of MSDE sp3a (on an XP
machine) without a SAPWD. Thanks.
Anthony
hi Anthony,
Anthony wrote:
> I was just wondering how I could install an instance of MSDE sp3a (on
> an XP machine) without a SAPWD. Thanks.
just provide the
BLANKSAPWD=1
parameter to the setup.exe boostrap installer...
http://msdn.microsoft.com/library/de...stsql_84xl.asp
BTW, just consider this is not a best practice... :D
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks a million. And I agree, probably not a best practice.
Anthony
"Andrea Montanari" wrote:

> hi Anthony,
> Anthony wrote:
> just provide the
> BLANKSAPWD=1
> parameter to the setup.exe boostrap installer...
> http://msdn.microsoft.com/library/de...stsql_84xl.asp
> BTW, just consider this is not a best practice... :D
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>

Monday, March 26, 2012

MSDE sa password - newbie

I downloaded and installed (somehow) MSDE a couple weeks ago but have not used it. Now I try to access MSDE using sa account but it does not accept an empty password and I do not remember providing one at install. MSDE appears to be installed because I se
e data files at C:\Program Files\Microsoft SQL Server\MSSQL$VSDOTNET\Data. Is there any way I can start using this install or do I need to start all over?
hi Mike,
"Mike" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:C864FCBB-655C-4D66-9DC4-9215C74A47C7@.microsoft.com...
> I downloaded and installed (somehow) MSDE a couple weeks ago but have not
used it. Now I try to
>access MSDE using sa account but it does not accept an empty password and I
do not remember
>providing one at install. MSDE appears to be installed because I see data
files at C:\Program
>Files\Microsoft SQL Server\MSSQL$VSDOTNET\Data. Is there any way I can
start using this install or
>do I need to start all over?
you probably changed the sa password...
try login in using a trusted authenticated Windows login member of the
sysadmin group
all sysadmin are granted privilege to modify password of other user...
then execute (osql, or the query tool of your choice)
EXEC sp_password @.new = 'new_password', @.loginame = 'sa'
in order to modify the forgotten sa pwd..
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
|||Hi,
If you have not provided a password for the SA login at installation time,
then it should be blank and it should accept it.
What I doubt is the Server name that you would be entering to connect to
the MSDE.
From the folder name that you have sent, I understand that it is a named
instance and you should use "computername\Instancename", in your case
"Computername\VSDOTNET", replace computername with the name of your
computer and try it.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.

MSDE Running on Two Computers in Workgroup Mode

I have two PC running Windows XP Pro in Workgroup Mode. They both in mixed
authentication mode with blank sa password.
The usernames on each machine are the same and they have no password.
The problem I have is with merge replication. The replication fails with the
message "Login failed for user 'sa'. Reason: Not associated with a trusted
SQL Server connection."
Both computers use the local system account to start the SQL server agent.
If we connect manually to the database via ADO using the sa with blank
password we have no difficulties.
Can someone please advise where I am going wrong.
Thank you in advance.
Colin
Hi ,
There are a number of reasons why this error may occur:
Try using these steps:
1) Most probably you may not be able to logon on to the sql server using
windows authentication.
2) Try using windows authentication over named pipes instead fo tcp/ip to
connect to the sql server.
Make sure that you make use of an alias to do the task
This should fix the problem.
Girish Sundaram
This posting is provided "AS IS" with no warranties, and confers no rights.

MSDE regualr maintenance - help

Hi folks
New to MSDE...
1. What is the best options to use when doing backups?
option 1. OSQL -U sa -P password -S server -Q "BACKUP DATABASE db1 TO DISK
= 'c:\Backups\backup1.bck'"
option 2. OSQL -U sa -P password -S server -Q "BACKUP DATABASE db1 TO DISK =
'C:\backups\backup1.bck' WITH FORMAT, STATS"
2. Should I also be doing a reindex? I would like to do a batch sql job (
like above backup)
USE DB1
GO
sp_msforeachtable @.command1 = 'DBCC DBREINDEX ([?])'
3. Should I do a Database check if yes, before or after backup...
dbcc checkdb ('database')
4. Would also like to get information DB size - just to mkae sure its stay's
under the 2GB limit.
Someone recommend the followinf - but not sure what they all do...
Save the following commands to a file named "WhatsUpMaint.bat":
osql -E -D WhatsUp -Q "DBCC SHRINKDATABASE (WhatsUp)"
osql -E -D WhatsUp -Q "EXEC sp_MsForEachTable 'DBCC DBREINDEX (''?'', '''',
0)'"
osql -E -D WhatsUp -Q "EXEC sp_createstats"
osql -E -D WhatsUp -Q "EXEC sp_updatestats"
osql -E -D WhatsUp -Q "EXEC sp_MsForEachTable 'sp_recompile ''?'''"
osql -E -D WhatsUp -Q "DBCC UPDATEUSAGE ('WhatsUp')"
osql -E -D WhatsUp -Q "EXEC sp_cycle_errorlog"
hi Danny,
Danny wrote:
> 1. What is the best options to use when doing backups?
> option 1. OSQL -U sa -P password -S server -Q "BACKUP DATABASE db1
> TO DISK = 'c:\Backups\backup1.bck'"
> option 2. OSQL -U sa -P password -S server -Q "BACKUP DATABASE db1 TO
> DISK = 'C:\backups\backup1.bck' WITH FORMAT, STATS"
the "bad thing" of this batch is that it includes sa's password in clear
text... please do not code a cmd/bat file this way :D
create a "backup" login with appropriate permissions and hardcode it's
credentials, not "sa" ones :D
WITH FORMAT specifies a new media set will be created.. so this depends on
your actual requirements.. if you want to "append" your current backup to
existing ones, do not specify it, else, do it..
STATS, on the other hand, specify to output backup percentage to the
standard output..
if not specified you usually have an output like
BACKUP DATABASE pubs TO DISK = 'c:\pus.bak';
--<--
Processed 248 pages for database 'pubs', file 'pubs' on file 4.
Processed 1 pages for database 'pubs', file 'pubs_log' on file 4.
BACKUP DATABASE successfully processed 249 pages in 0.073 seconds (27.942
MB/sec).
where
BACKUP DATABASE pubs TO DISK = 'c:\pus.bak'
WITH STATS;
--<--
12 percent processed.
22 percent processed.
32 percent processed.
41 percent processed.
51 percent processed.
61 percent processed.
70 percent processed.
80 percent processed.
93 percent processed.
Processed 248 pages for database 'pubs', file 'pubs' on file 5.
100 percent processed.
Processed 1 pages for database 'pubs', file 'pubs_log' on file 5.
BACKUP DATABASE successfully processed 249 pages in 0.069 seconds (29.562
MB/sec).
if you do not specify a percent value, SQL Server uses a default of 10%..

> 2. Should I also be doing a reindex? I would like to do a batch sql
> job ( like above backup)
> USE DB1
> GO
> sp_msforeachtable @.command1 = 'DBCC DBREINDEX ([?])'
this statement uses an undocumented stored procedure, sp_msforeachtable, to
rebuild all indexes of each table object.. this obviously imply
"rebuilding" the whole table with clustered index.. so this implies both
time and file related implications... have a look at
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
for futher info, but, to our interest, reindexing is usually a "good thing"
to do :D

> 3. Should I do a Database check if yes, before or after backup...
> dbcc checkdb ('database')
you can go pre-backup

> 4. Would also like to get information DB size - just to mkae sure its
> stay's under the 2GB limit.
sorry, did not understand your requirement...

> Save the following commands to a file named "WhatsUpMaint.bat":
> osql -E -D WhatsUp -Q "DBCC SHRINKDATABASE (WhatsUp)"
about shrinking a database you can have a look at Tibor Karaszi's (SQL
Server MVP) article at http://www.karaszi.com/SQLServer/info_dont_shrink.asp
about the trusted connection you use here... -E indicates to connect as the
current logged in account.. and, as the statements you are executing require
high permissions in the instance context, this means the current interactive
Windows account is quite an admin... as this sounds to be a scheduled batch,
I'd opt for other credentials in order not to require to log in as such a
super man :D

> osql -E -D WhatsUp -Q "EXEC sp_MsForEachTable 'DBCC DBREINDEX (''?'',
> '''', 0)'"
> osql -E -D WhatsUp -Q "EXEC sp_createstats"
to my head this is not required as you usually set this at database level so
that statistics always are created and updated..

> osql -E -D WhatsUp -Q "EXEC sp_updatestats"
but this can be maintained as statistics are "rebuilt" when a certain
treshhold of changes is reached, so you can force it..

> osql -E -D WhatsUp -Q "EXEC sp_MsForEachTable 'sp_recompile ''?'''"
not correct.. this one is available for stored procedures only and not for
base tables...
causing the procedures to be recompiled at next execution time will
obviously imply penalties in their execution... I do usually not perform
that one..

> osql -E -D WhatsUp -Q "DBCC UPDATEUSAGE ('WhatsUp')"
this one re-syncs catalog's stats.. I do usually not do that if not
required.. but it does not hurt..

> osql -E -D WhatsUp -Q "EXEC sp_cycle_errorlog"
this one changes the current log to a new created one... I really do not do
that if not required in order to have a troubleshoot log to archive so some
reason.. but it does not imply penaltie/problems at all..
at the end of the game, I'd suggest to "log" the results of your
maintenances outputting them to a text file you can later inspect, send by
mail or whatever..
just add the
>filePathAndName.txt
parameter to your 1st oSql call to initilize your file and add[vbcol=seagreen]
parameter to the other ones, causing the results to be appended to that
file...
regards
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply

Friday, March 23, 2012

MSDE password change for "sa"

Hello,
If I can get into the default instance of MSDE using a Windows
account (trusted connection) using 'osql -E' is it possible for me to
change the 'sa' SQL account if I don't know the current password? The
Windows account is a domain admin and local box admin if that matters.
Also, can anyone point me to a Q article that will give me a step
by step on how to upgrade from MSDE to SQL so I can get past this 2GB
limitation?
If anyone can answer these I am definitely buying beers!!
Thanks,
Dan
If you can login as an admin on the box and the
builtin\administrators group login was not removed or
modified, you will be logged in as a member of the sysadmins
server role. As a sysadmin, you can execute the following to
change the sa password:
sp_password NULL, 'NewSaPassword', 'sa'
Upgrading to SQL Server isn't too bad. Run the SQL Server
installation CD. You will be asked if you want to upgrade
your existing instance or install a new one. Choose to
upgrade.
For more detailed steps on upgrading, you can refer to the
SQL Server Books Online topic:
How to perform an edition upgrade within SQL Server 2000
(Setup)
http://msdn.microsoft.com/library/en...stall_1d7y.asp
-Sue
On 15 Jun 2004 17:41:11 -0700, dankennedy24@.hotmail.com (Dan
Kennedy) wrote:

>Hello,
> If I can get into the default instance of MSDE using a Windows
>account (trusted connection) using 'osql -E' is it possible for me to
>change the 'sa' SQL account if I don't know the current password? The
>Windows account is a domain admin and local box admin if that matters.
> Also, can anyone point me to a Q article that will give me a step
>by step on how to upgrade from MSDE to SQL so I can get past this 2GB
>limitation?
>If anyone can answer these I am definitely buying beers!!
>Thanks,
>Dan
|||But the current "sa" password isn't blank... will that statement still
work? I login to the machine as a local admin and connect via the
osql statement as the same ID as I logon to the machine with.
Sue Hoegemeier <Sue_H@.nomail.please> wrote in message news:<np8vc0p2v2lfj8ke5mm0vf6f8vmrfg9plg@.4ax.com>. ..[vbcol=seagreen]
> If you can login as an admin on the box and the
> builtin\administrators group login was not removed or
> modified, you will be logged in as a member of the sysadmins
> server role. As a sysadmin, you can execute the following to
> change the sa password:
> sp_password NULL, 'NewSaPassword', 'sa'
> Upgrading to SQL Server isn't too bad. Run the SQL Server
> installation CD. You will be asked if you want to upgrade
> your existing instance or install a new one. Choose to
> upgrade.
> For more detailed steps on upgrading, you can refer to the
> SQL Server Books Online topic:
> How to perform an edition upgrade within SQL Server 2000
> (Setup)
> http://msdn.microsoft.com/library/en...stall_1d7y.asp
> -Sue
> On 15 Jun 2004 17:41:11 -0700, dankennedy24@.hotmail.com (Dan
> Kennedy) wrote:
|||Yes...it will still work. That's what you would use to reset any
password when you are logged in as a sysadmin. Just pass null for the
old password. It doesn't mean the password is null. It means you
aren't supplying the old password.
-Sue
On 16 Jun 2004 11:26:10 -0700, dankennedy24@.hotmail.com (Dan Kennedy)
wrote:
[vbcol=seagreen]
>But the current "sa" password isn't blank... will that statement still
>work? I login to the machine as a local admin and connect via the
>osql statement as the same ID as I logon to the machine with.
>Sue Hoegemeier <Sue_H@.nomail.please> wrote in message news:<np8vc0p2v2lfj8ke5mm0vf6f8vmrfg9plg@.4ax.com>. ..

MSDE password change for "sa"

Hello,
If I can get into the default instance of MSDE using a Windows
account (trusted connection) using 'osql -E' is it possible for me to
change the 'sa' SQL account if I don't know the current password? The
Windows account is a domain admin and local box admin if that matters.
Also, can anyone point me to a Q article that will give me a step
by step on how to upgrade from MSDE to SQL so I can get past this 2GB
limitation?
If anyone can answer these I am definitely buying beers!!
Thanks,
DanIf you can login as an admin on the box and the
builtin\administrators group login was not removed or
modified, you will be logged in as a member of the sysadmins
server role. As a sysadmin, you can execute the following to
change the sa password:
sp_password NULL, 'NewSaPassword', 'sa'
Upgrading to SQL Server isn't too bad. Run the SQL Server
installation CD. You will be asked if you want to upgrade
your existing instance or install a new one. Choose to
upgrade.
For more detailed steps on upgrading, you can refer to the
SQL Server Books Online topic:
How to perform an edition upgrade within SQL Server 2000
(Setup)
http://msdn.microsoft.com/library/en-us/howtosql/ht_install_1d7y.asp
-Sue
On 15 Jun 2004 17:41:11 -0700, dankennedy24@.hotmail.com (Dan
Kennedy) wrote:
>Hello,
> If I can get into the default instance of MSDE using a Windows
>account (trusted connection) using 'osql -E' is it possible for me to
>change the 'sa' SQL account if I don't know the current password? The
>Windows account is a domain admin and local box admin if that matters.
> Also, can anyone point me to a Q article that will give me a step
>by step on how to upgrade from MSDE to SQL so I can get past this 2GB
>limitation?
>If anyone can answer these I am definitely buying beers!!
>Thanks,
>Dan|||But the current "sa" password isn't blank... will that statement still
work? I login to the machine as a local admin and connect via the
osql statement as the same ID as I logon to the machine with.
Sue Hoegemeier <Sue_H@.nomail.please> wrote in message news:<np8vc0p2v2lfj8ke5mm0vf6f8vmrfg9plg@.4ax.com>...
> If you can login as an admin on the box and the
> builtin\administrators group login was not removed or
> modified, you will be logged in as a member of the sysadmins
> server role. As a sysadmin, you can execute the following to
> change the sa password:
> sp_password NULL, 'NewSaPassword', 'sa'
> Upgrading to SQL Server isn't too bad. Run the SQL Server
> installation CD. You will be asked if you want to upgrade
> your existing instance or install a new one. Choose to
> upgrade.
> For more detailed steps on upgrading, you can refer to the
> SQL Server Books Online topic:
> How to perform an edition upgrade within SQL Server 2000
> (Setup)
> http://msdn.microsoft.com/library/en-us/howtosql/ht_install_1d7y.asp
> -Sue
> On 15 Jun 2004 17:41:11 -0700, dankennedy24@.hotmail.com (Dan
> Kennedy) wrote:
> >Hello,
> > If I can get into the default instance of MSDE using a Windows
> >account (trusted connection) using 'osql -E' is it possible for me to
> >change the 'sa' SQL account if I don't know the current password? The
> >Windows account is a domain admin and local box admin if that matters.
> > Also, can anyone point me to a Q article that will give me a step
> >by step on how to upgrade from MSDE to SQL so I can get past this 2GB
> >limitation?
> >
> >If anyone can answer these I am definitely buying beers!!
> >
> >Thanks,
> >Dan|||Yes...it will still work. That's what you would use to reset any
password when you are logged in as a sysadmin. Just pass null for the
old password. It doesn't mean the password is null. It means you
aren't supplying the old password.
-Sue
On 16 Jun 2004 11:26:10 -0700, dankennedy24@.hotmail.com (Dan Kennedy)
wrote:
>But the current "sa" password isn't blank... will that statement still
>work? I login to the machine as a local admin and connect via the
>osql statement as the same ID as I logon to the machine with.
>Sue Hoegemeier <Sue_H@.nomail.please> wrote in message news:<np8vc0p2v2lfj8ke5mm0vf6f8vmrfg9plg@.4ax.com>...
>> If you can login as an admin on the box and the
>> builtin\administrators group login was not removed or
>> modified, you will be logged in as a member of the sysadmins
>> server role. As a sysadmin, you can execute the following to
>> change the sa password:
>> sp_password NULL, 'NewSaPassword', 'sa'
>> Upgrading to SQL Server isn't too bad. Run the SQL Server
>> installation CD. You will be asked if you want to upgrade
>> your existing instance or install a new one. Choose to
>> upgrade.
>> For more detailed steps on upgrading, you can refer to the
>> SQL Server Books Online topic:
>> How to perform an edition upgrade within SQL Server 2000
>> (Setup)
>> http://msdn.microsoft.com/library/en-us/howtosql/ht_install_1d7y.asp
>> -Sue
>> On 15 Jun 2004 17:41:11 -0700, dankennedy24@.hotmail.com (Dan
>> Kennedy) wrote:
>> >Hello,
>> > If I can get into the default instance of MSDE using a Windows
>> >account (trusted connection) using 'osql -E' is it possible for me to
>> >change the 'sa' SQL account if I don't know the current password? The
>> >Windows account is a domain admin and local box admin if that matters.
>> > Also, can anyone point me to a Q article that will give me a step
>> >by step on how to upgrade from MSDE to SQL so I can get past this 2GB
>> >limitation?
>> >
>> >If anyone can answer these I am definitely buying beers!!
>> >
>> >Thanks,
>> >Dan

MSDE password change for "sa"

Hello,
If I can get into the default instance of MSDE using a Windows
account (trusted connection) using 'osql -E' is it possible for me to
change the 'sa' SQL account if I don't know the current password? The
Windows account is a domain admin and local box admin if that matters.
Also, can anyone point me to a Q article that will give me a step
by step on how to upgrade from MSDE to SQL so I can get past this 2GB
limitation?
If anyone can answer these I am definitely buying beers!!
Thanks,
DanIf you can login as an admin on the box and the
builtin\administrators group login was not removed or
modified, you will be logged in as a member of the sysadmins
server role. As a sysadmin, you can execute the following to
change the sa password:
sp_password NULL, 'NewSaPassword', 'sa'
Upgrading to SQL Server isn't too bad. Run the SQL Server
installation CD. You will be asked if you want to upgrade
your existing instance or install a new one. Choose to
upgrade.
For more detailed steps on upgrading, you can refer to the
SQL Server Books Online topic:
How to perform an edition upgrade within SQL Server 2000
(Setup)
http://msdn.microsoft.com/library/e...nstall_1d7y.asp
-Sue
On 15 Jun 2004 17:41:11 -0700, dankennedy24@.hotmail.com (Dan
Kennedy) wrote:

>Hello,
> If I can get into the default instance of MSDE using a Windows
>account (trusted connection) using 'osql -E' is it possible for me to
>change the 'sa' SQL account if I don't know the current password? The
>Windows account is a domain admin and local box admin if that matters.
> Also, can anyone point me to a Q article that will give me a step
>by step on how to upgrade from MSDE to SQL so I can get past this 2GB
>limitation?
>If anyone can answer these I am definitely buying beers!!
>Thanks,
>Dan|||But the current "sa" password isn't blank... will that statement still
work? I login to the machine as a local admin and connect via the
osql statement as the same ID as I logon to the machine with.
Sue Hoegemeier <Sue_H@.nomail.please> wrote in message news:<np8vc0p2v2lfj8ke5mm0vf6f8vmrfg9p
lg@.4ax.com>...[vbcol=seagreen]
> If you can login as an admin on the box and the
> builtin\administrators group login was not removed or
> modified, you will be logged in as a member of the sysadmins
> server role. As a sysadmin, you can execute the following to
> change the sa password:
> sp_password NULL, 'NewSaPassword', 'sa'
> Upgrading to SQL Server isn't too bad. Run the SQL Server
> installation CD. You will be asked if you want to upgrade
> your existing instance or install a new one. Choose to
> upgrade.
> For more detailed steps on upgrading, you can refer to the
> SQL Server Books Online topic:
> How to perform an edition upgrade within SQL Server 2000
> (Setup)
> http://msdn.microsoft.com/library/e...nstall_1d7y.asp
> -Sue
> On 15 Jun 2004 17:41:11 -0700, dankennedy24@.hotmail.com (Dan
> Kennedy) wrote:
>|||Yes...it will still work. That's what you would use to reset any
password when you are logged in as a sysadmin. Just pass null for the
old password. It doesn't mean the password is null. It means you
aren't supplying the old password.
-Sue
On 16 Jun 2004 11:26:10 -0700, dankennedy24@.hotmail.com (Dan Kennedy)
wrote:
[vbcol=seagreen]
>But the current "sa" password isn't blank... will that statement still
>work? I login to the machine as a local admin and connect via the
>osql statement as the same ID as I logon to the machine with.
>Sue Hoegemeier <Sue_H@.nomail.please> wrote in message news:<np8vc0p2v2lfj8k
e5mm0vf6f8vmrfg9plg@.4ax.com>...

MSDE Password

I have a MSDE database running with my sharepoint portal and now i want to customize the portal with some pages built in webmatrix, but i am getting a huge problem. i just don't know what he MSDE password is. how may i find it out, change it or even break it?well, if it's set up with default options, the machine's administrator account should be able to access it without needing the sa password.|||Hi Atrax,

thxs for the support. I've tryied that but didn't work. I type "osql -U sa" and set the password for blank and got the wrong password message, then i tried with the administrator's username and password with the same results. What should i do now? To just uninstall and reinstall it isn't an option because it's the firm's intranet and it can't stop working.|||Problem solved by reinstalation, :(.sql

MSDE Password

I'm trying to apply a password to the (sa) account. When
I go to the dos prompt I type
osql -U sa
password:
1>sp_password @.old = null
2>@.new = 'password'
3>@.loginame = 'sa'
4>go
Then I get this error message
Msg 170, Level 15, State 1, Server _____, Line 2
Line 2: Incorrect syntax near '@.new'
what am i doing wrong
Try commas in between parameters like so:
1>sp_password @.old = null,
2>@.new = 'password',
3>@.loginame = 'sa',
4>go,
Bob
SuccessWare Software
"mcarter297" <anonymous@.discussions.microsoft.com> wrote in message
news:1d48001c453bc$190dfa40$a101280a@.phx.gbl...
> I'm trying to apply a password to the (sa) account. When
> I go to the dos prompt I type
> osql -U sa
> password:
> 1>sp_password @.old = null
> 2>@.new = 'password'
> 3>@.loginame = 'sa'
> 4>go
> Then I get this error message
> Msg 170, Level 15, State 1, Server _____, Line 2
> Line 2: Incorrect syntax near '@.new'
> what am i doing wrong
|||Hi,
OSQL -Usa -Ppasword -S Servername (Enter Key)
1>sp_password null,'newpassword',sa (Enter key)
2>go (Enter Key)
Thanks
Hari
MCDBA
"mcarter297" <anonymous@.discussions.microsoft.com> wrote in message
news:1d48001c453bc$190dfa40$a101280a@.phx.gbl...
> I'm trying to apply a password to the (sa) account. When
> I go to the dos prompt I type
> osql -U sa
> password:
> 1>sp_password @.old = null
> 2>@.new = 'password'
> 3>@.loginame = 'sa'
> 4>go
> Then I get this error message
> Msg 170, Level 15, State 1, Server _____, Line 2
> Line 2: Incorrect syntax near '@.new'
> what am i doing wrong

Friday, March 9, 2012

MSDE installation problems

hi

i have downloaded the free MSDERelA from the official website but when i wanna run the installation, it says

"A strong SA password is needed for security reasons.Please use the SAPWD switch to supply the same"

i read the readme doc but i still cant understand how to install n where to find the SAPWD switch ??

Please guide me
Thank you very muchInstructions here

Wednesday, March 7, 2012

MSDE Install Question

I installed MSDE using Windows authentication and gave the SA logon ID a
"strong" password. However, when I attempt to logon to the MSDE database
(via OSQL) I get a message stating something to the effect of "the logon ID
is not associated with a trusted account". I realize what this means (i.e.
the logon ID "sa" is not a Windows account). However, what I'm wondering is
how do I logon to a brand new (MSDE) server once it's been installed to use
Windows authentication if I haven't setup any accounts/roles yet?
-- Thanks, Jeff
hi Jeff,
Jeff B. wrote:
> I installed MSDE using Windows authentication and gave the SA logon
> ID a "strong" password. However, when I attempt to logon to the MSDE
> database (via OSQL) I get a message stating something to the effect
> of "the logon ID is not associated with a trusted account". I
> realize what this means (i.e. the logon ID "sa" is not a Windows
> account). However, what I'm wondering is how do I logon to a brand
> new (MSDE) server once it's been installed to use Windows
> authentication if I haven't setup any accounts/roles yet?
> -- Thanks, Jeff
by default, the Windows administrators group will be mapped to the SQL
Server BUILTIN\Administrators WinNT group, so you can log in as a Windows
admin..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Saturday, February 25, 2012

MSDE Install

When I tried to install MSDE I got message :
"A strong SA password is required for security reasons. Please use SAPWD switch to supply the same."

What should I do ? I'm using XP pro and VS 2003You have to specify a password

Type Setup SAPWD=(Some password) SecurityMode=SQL

See here

http://www.asp.net/msde/Default.aspx?tabindex=0&tabid=1

Instruction 2|||I'be tryed it and it didn't work. Can we Install MSDE on XP Pro ?
Jeff|||Yes you can install MSDE on XP Pro. You can also use Access 2002 to connect to SQL Server or MSDE by creating a project file.

Cheers|||Sounds interesting...how can you connect to MSDE with Access ?
Thanks,
Jeff