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

Wednesday, March 21, 2012

Issues with MSDE after installing WMSDE, WSUS

I have a stable 3rd party application which has been running on MSDE Sp3 (ver
2000.80.760.0) as the default instance. I installed WSUS, which apparently
uses WMSDE (version 2000.80.884.0), as a named instance. After this
installation I noticed that the original SQL server has a memory leak,
consuming the resources of the server over a few hours.
I upgraded (replaced) the Sp3 default instance with Sp4 (version
2000.80.2039.0). Howeveer the problem seems to be continuing. Is it wise to
have these 2 different database versions running on the same machine or
should I separate/amalgamate them?
TIA
hi,
Lance wrote:
> I have a stable 3rd party application which has been running on MSDE
> Sp3 (ver 2000.80.760.0) as the default instance. I installed WSUS,
> which apparently uses WMSDE (version 2000.80.884.0), as a named
> instance. After this installation I noticed that the original SQL
> server has a memory leak, consuming the resources of the server over
> a few hours.
> I upgraded (replaced) the Sp3 default instance with Sp4 (version
> 2000.80.2039.0). Howeveer the problem seems to be continuing. Is it
> wise to have these 2 different database versions running on the same
> machine or should I separate/amalgamate them?
> TIA
WMSDE is a modified version of MSDE that enables db size larger then 2gb per
database, that is one of the constraints/limitations of "standard" MSDE, and
is provided for SharePoint, AFAIK..
unfortunately no sp4 for this edition has still been provided, even if it
has been promised...
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
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
sql

Monday, March 19, 2012

Issues Renaming Analysis Server Instance

Hi Friends

I want to rename My Analysis Services Instance installed on E: Drive. I read an article how to rename the Analysis Service Instance . Then I followed 64-bit path to rename, but it gives the following error rolling back to the original Instance Name:

Registering the new performance counters file:

LoadPerfCounterTextStrings for file C:\Program Files\Microsoft SQL Server\MSSQL.1\OLAP\bin\msmdctr.ini failed with error code 2

The System cannot find the file Specified

Has anybody came across this issue. Any workarounds ?

Thanks

Subhash Subramanyam.

Hi Subash,

I need few more info from you before I troubleshoot the issue.

1) What was the intial folder your Analysis Service resides? ex: E:\program files\mssql.1\olap\bin

2) What was the original instance name and what did you rename to?

3) Do you get this error from asinstancerename tool?

Thanks,

Deva

|||

1) What was the intial folder your Analysis Service resides? ex: E:\program files\mssql.1\olap\bin

C:\Program Files\Microsoft SQL Server\MSSQL.1\OLAP\bin

2) What was the original instance name and what did you rename to?

original instance name: ss2005

rename to: as2005

3) Do you get this error from asinstancerename tool?

Yes

Hope this helps.

Thanks

Subhash Subramanyam

Monday, February 20, 2012

isqlw won't start

Hi there,

I tried to install MS SQL Server 2000 on my desktop computer after
uninstalling a version 7 instance. Everything worked fine. Using
Enterprise Manager I can manage databases and the database enginge itself.

My problem is now, that ISQLW.exe, i.e Query Analayzer won't start. The
taskmanager shows a process isqlw.exe but nothing happens. MSSQL Log
files give no hints, neither does the Windows 2000 event log.

I assume a problem with the previously installed MSSQL7 version, but
walked through the registry as well.

Are there any hints why isqlw doesn't want to speak to me?

Thanks,
AndreAndre Ma@.ss schrieb:

Quote:

Originally Posted by

Are there any hints why isqlw doesn't want to speak to me?


Meanwhile I have solved the problem. I have installed SP3 and have
repaired the registry entries. After that Query Analyzer worked fine.

Thanks,
Andre|||Andre Ma@.ss (Samweis11@.gmx.de) writes:

Quote:

Originally Posted by

I tried to install MS SQL Server 2000 on my desktop computer after
uninstalling a version 7 instance. Everything worked fine. Using
Enterprise Manager I can manage databases and the database enginge itself.
>
My problem is now, that ISQLW.exe, i.e Query Analayzer won't start. The
taskmanager shows a process isqlw.exe but nothing happens. MSSQL Log
files give no hints, neither does the Windows 2000 event log.
>
I assume a problem with the previously installed MSSQL7 version, but
walked through the registry as well.
>
Are there any hints why isqlw doesn't want to speak to me?


Tried rebooting? More importantly, have you installed any service pack
for SQL 2000? You should install at least SP3, but there is an SP4 as
well. There is a serious security threat in SQL 2000 RTM which is fixed
in SP3. (The Slammer worm.)

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx