MSDE and Computer Name Change

Hi!
I know that the default instance of MSDE is the computer name. If the
computer's name is subsequently changed, will the default instance’s name
change to the new computer name as well.
Thanks for your thoughts.
Actually the default instance name is not the computer name. All instances
are addressed in connections strings as <computer name>\<instance name>. If
you leave off the instance name then SQL Server assumes you are talking
about the default instance. So yes, if you change the computer name, all
your connection strings will break, probably including some that you aren't
aware of so changing the computer name is a risky thing to do. At a minimum
you will nee to use sp_addserver and restart MSDE to change SQL Server's
local server name.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Gene" <Gene@.discussions.microsoft.com> wrote in message
news:85740AA2-9F4B-4CF8-B304-E27782458703@.microsoft.com...
> Hi!
> I know that the default instance of MSDE is the computer name. If the
> computer's name is subsequently changed, will the default instance's name
> change to the new computer name as well.
> Thanks for your thoughts.
|||Thanks for the input Roger. I don't know much about SQL, but my guess would
have been pretty close to your response. I'm concerned about breaking
something I'm not aware of and not knowing where to go from there.
Regards,
Gene
"Roger Wolter[MSFT]" wrote:

> Actually the default instance name is not the computer name. All instances
> are addressed in connections strings as <computer name>\<instance name>. If
> you leave off the instance name then SQL Server assumes you are talking
> about the default instance. So yes, if you change the computer name, all
> your connection strings will break, probably including some that you aren't
> aware of so changing the computer name is a risky thing to do. At a minimum
> you will nee to use sp_addserver and restart MSDE to change SQL Server's
> local server name.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Gene" <Gene@.discussions.microsoft.com> wrote in message
> news:85740AA2-9F4B-4CF8-B304-E27782458703@.microsoft.com...
>
>
sql

MSDE 2000 Install Problem

Hi
I am trying to install MSDE 2000 sp3 on a Windows XP that has had a previous
installation in the past. The previous installation has been removed, but
when I try installing MSDE again from the command prompt, it starts to set
up the gives me an error saying installation failed.
I have deleted the Microsoft SQL Server directory from Program Files,
cleaned out all registry entries for the instance name and have run the
install using the following command:
Setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1
SAPWD=<password>
Obviously replacing <password> with an appropriate password.
Are there any other known issues that anyone knows that will get this
installation working? Any advice would be appreciated.
Regards
Jason
hi Jason,
please add the
/L*v 'c:\...\log.txt'
parameter, in order to get a 2mb log file for the installation, where you
can search for
"value 3"
as error indication
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

msde 2000 install failes on xp

Hi
I cant install MSDE 2000 on one XP machine
Cant figure out whats wrong
Because log file too large
Download it here
www.deltmar.ee/logfile.zip
Regards;
Mex
hi Mex,
Meelis Lilbok wrote:
> Hi
> I cant install MSDE 2000 on one XP machine
> Cant figure out whats wrong
> Because log file too large
> Download it here
> www.deltmar.ee/logfile.zip
>
the relevant part of the log is
Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
Action ended 14:59:46: InstallFinalize. Return value 3.
usually depending on re-intallation on partially cleaned machines..
please have a look at
http://support.microsoft.com/default...99&Product=sql
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE 2000 and ODBC (Connection failed)

Hi
I Installed MSDE 2000 and try to connect with it via ODBC.
I want the connection with SQL Server authentication using a login ID "sa" and blank password
But it is dispaly this message:
====================
Connection failed:
SQLState:'28000'
SQL Server Error:18456
[Microsoft][ODBC Sql Server Driver][SQL Server]Login failed for user 'sa'
====================check what authentication method your msde is using and make sure that standard security is available.|||Thanks ms_sql_dba

My MSDE use both WINDOWS/SQL Server authentication
I check "LoginMode" value in REGISTRY it's = Zero which mean both|||Thanks ms_sql_dba

My MSDE use both WINDOWS/SQL Server authentication
I check "LoginMode" value in REGISTRY it's = Zero which mean both|||Up 4 Help|||I found the Solution in Archive which guide me to this link:
http://www.dbforums.com/showthread.php?threadid=711306

The Solution is very simple:
Change "SA" password

use this command line in DOS:
osql -Q"exec sp_password null,'newpassword','sa'" -E

Msde 2000

Hi

I installed the MSDE that comes with Office 2000. When connecting to my mdf, I received an error saying that the header file is invalid. I understand that the MSDE shipped with Office 2000 uses the SQL 7 engine, therefore it does not recognize the my SQL 2000 database file format. Can someone tell me where can I get a copy of the correct version of MSDE that will work with my SQL 2000 mdf?

Thanks

SHKMSDE 2000 (http://www.microsoft.com/sql/msde/downloads/download.asp)|||Thank You

MSDE + SSL

Hi!
I had a working Win2003 server with Backup Exec 9.1 and Exchange 2003 OWA.
I installed SP1 for Win2003, WSUS and I created a certificate for OWA with
help from SelfSSL.
After this, I cant start my Backup Exec services, complaining about some SSL
error:
SSL Security error
ConnectionOpen (SECDoHandshake()).
and
[DBNETLIB][ConnectionOpen (SECDoHandshake()).]SSL Security error.
I think all this is a problem with SSL and MSDE.
Veritas says "talk to Microsoft" and gues what MS says...
What does SelfSSL to do with MSDE? Or what shoult I do to make MSDE (8.0)
run nice beside SSL for our OWA access.
Thanks!
Mattias
hi Mattias,
MrM wrote:
> Hi!
> I had a working Win2003 server with Backup Exec 9.1 and Exchange 2003
> OWA. I installed SP1 for Win2003, WSUS and I created a certificate
> for OWA with help from SelfSSL.
> After this, I cant start my Backup Exec services, complaining about
> some SSL error:
> --
> SSL Security error
> ConnectionOpen (SECDoHandshake()).
> and
> [DBNETLIB][ConnectionOpen (SECDoHandshake()).]SSL Security error.
> --
> I think all this is a problem with SSL and MSDE.
> Veritas says "talk to Microsoft" and gues what MS says...
> What does SelfSSL to do with MSDE? Or what shoult I do to make MSDE
> (8.0) run nice beside SSL for our OWA access.
>
please try having a look at
http://support.microsoft.com/default.aspx?id=309398 and
http://www.fftf.org/news/Aug05feed/M...ouble.rss.html
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE - Just Stops!

Hi:
I have a Win2000 server that has been running MSDE for about five months.
Suddenly today it just stopped running.
There were no entries in the event viewer or anything. I stopped and
restarted the service and it still did not respond.
Finally I rebooted the computer and it's working once again. I rebooted the
machine last night so it had only been running about 12 hours and was
functional this morning.
Does anyone have any suggestions on how to determine what happened - and
prevent it from happening in the future?
Thanks for your help!
Fred
Hi,
Verify the SQL Server Logs as well for any errors. It is always recommented
to check the logs atleast once a day.
Check if there is any memory leak 3rd paqrt programs in ur server.
Thanks
Hari
SQL Server MVP
"Fred Nelson" <fred@.smartybird.com> wrote in message
news:umZDRJNUFHA.2664@.TK2MSFTNGP15.phx.gbl...
> Hi:
> I have a Win2000 server that has been running MSDE for about five months.
> Suddenly today it just stopped running.
> There were no entries in the event viewer or anything. I stopped and
> restarted the service and it still did not respond.
> Finally I rebooted the computer and it's working once again. I rebooted
the
> machine last night so it had only been running about 12 hours and was
> functional this morning.
> Does anyone have any suggestions on how to determine what happened - and
> prevent it from happening in the future?
> Thanks for your help!
> Fred
>

msdb recovery on sql 2005

Hi

I have a backup of msdb on sql 2005 version 9.00.2047

I need to use this backup to restore msdb on the same machine.

But the version has been upgraded to 9.00.2153

All of my attempts end up with the same messages

"...cannot be restored because it was created by a different version of the server..."

Thanks.

You are going to have to find an install of version 9.00.2047, restore the msdb database, upgrade the instance to 9.00.2153, backup the msdb database again, and then use that backup to restore to the instance that you want.

There is a reason that every hotfix and service pack has an explicit warning message that you must backup system databases immediately after applying the service pack or hotfix. You can not restore a system database across hotfix or service pack versions.

|||Thanks it worked as you said.

msdb database problem with MS SQL Server 6.5

Hi
I have a problem creating a backup in SQL Server 6.5. Although, the
backup produced does restore ok, I want to stop this error message
appearing everytime I make a backup. The error message is:

"
[SQL Server ]Can't allocate space for object 'sysbackupdetail' in
database 'msdb' because the 'default' segment is full. If you ran out
of space in Syslogs, dump the transaction log. Otherwise, use ALTER
DATABASE or sp_extendsegment to increase the size of the segment.
"

this articles appears to describe the problem and the solution:

http://support.microsoft.com/defaul...kb;EN-US;152354

It recommends creating a stored procedure to delete old entries. The
stored procedure cannot be created due tro a memory problem. What I
was wondering, although the article doesn't mention it, can a new
device be created and added to the msdb database. This should fix the
problem or is there problems doing this ?

Thanks in advance"John Mullan" <smurf010@.hotmail.com> wrote in message
news:92554ef7.0402040935.6fce79f1@.posting.google.c om...
> Hi
> I have a problem creating a backup in SQL Server 6.5. Although, the
> backup produced does restore ok, I want to stop this error message
> appearing everytime I make a backup. The error message is:
> "
> [SQL Server ]Can't allocate space for object 'sysbackupdetail' in
> database 'msdb' because the 'default' segment is full. If you ran out
> of space in Syslogs, dump the transaction log. Otherwise, use ALTER
> DATABASE or sp_extendsegment to increase the size of the segment.
> "
> this articles appears to describe the problem and the solution:
> http://support.microsoft.com/defaul...kb;EN-US;152354
> It recommends creating a stored procedure to delete old entries. The
> stored procedure cannot be created due tro a memory problem. What I
> was wondering, although the article doesn't mention it, can a new
> device be created and added to the msdb database. This should fix the
> problem or is there problems doing this ?
> Thanks in advance

I think (from memory) SQL6.5 already has a system stored procedure to clean
up the history for you - look for one called sp_purgehistory or something
similar, and check what the code does. Otherwise, extending the device
should work.

Simon