Analysis service: pb when archiving/restoring from 1 machine to another

I have to install cubes on another machine (not on the same site/NT domain).
I have archived the OLAP db and generated a .cab file.

I have retored on the destination server.
It works fine in Analysis Manager console (I can process and lokk at the data).
But when I want to access the cube from Excel using OLAP cube, I have an error msg.

Is there something I need to do on the distination server ?
Langage, SP, role, version of SQLServer/Analysis services ...

ThanksWhat is the error message that you get?|||In Excel: (translated from French)
"OLAP cube not found
OLAP database ha been modified or you do not have necessary authorisation to connect to the cube
Contact your database admin"

It has something to do wuth SSPI authentication ?|||It could have something to do with the access rights...
I once saw something similar to this, and then the problem was solved by adding the user account to the OLAP admin group.

Analysis of a 400GB database after SQL server restarts takes forever (or maybe hang)

Hello there,

We have a database used by a thrid party application that is 400GB in size. After the server gave some warnings, we restarted the machine and SQL server is doing an analysis on the database so it can be recovered. The recovery analysis of the 400GB database has been run for 3 days and only 7% complete. I doubt it'll ever finish. Because this recovery analysis is a background process which I can not kill, I can not drop the database either because it places an exclusive lock on the database when SQL server is doing analysis. We're using SQL server 2000 enterprise edition, sp3. Now I think that we probably should not have such a big database in the first place. Right now, I just want to stop the analysis if I can so I can either truncate the tables in that 400GB or drop the database completely. Not sure if start sql server in cmd with single user mode can do or not. Any suggestions are appreciated.

thanks,

-Jessie

if the database is not important and you do have a copy of it backed up, you can terminate sqlserver service; start a new session in console mode and drop the database.

e.g.

sqlservr.exe -c -f -m

|||

Thanks OJ for your reply! This database is important but we can't afford every time the server restarts, it takes 1 day to only recover 3% of this db. That "-f" stops the recovery of the user databases. But when I tried to run "use 400GBdb", it gave me this error:Server: Msg 913, Level 16, State 4, Line 1
Could not find database ID 12. Database may not be activated yet or may be in transition.

I'll first back the data/log files to tape before I drop the db. But are you sure I can drop the db even the system can not find the dbid?

-Jessie

|||

Jessie,

You can start sqlserver without doing any recovery of any user databases.

e.g.

sqlservr.exe -s"your_instance" -f -m

then connect to the instance and drop the database

drop database "your_db"

|||

Jessie,

You can start sqlserver without doing any recovery of any user databases.

e.g.

sqlservr.exe -s"your_instance" -f -m

then connect to the instance and drop the database

drop database "your_db"

|||

Thanks OJ! Yes, using -f can stop recovery of user database. But because user db is not recovered, they are not accessible. You'll get:dbid not found error. I rebooted the SQL serve twice and both recovery of the 400GB hung when the recovery is 99% complete. From SQL server error log: The Scheduler 3 appears to be hung. SPID 17, ECID 0, UMS Context 0x03716938. I guess 400 GB is beyong SQL server 2000 limit.

What I did is that I stopped the SQL server, delete the log file and restarted the SQL server. Then the db is marked as suspect and I deleted the db.

An internal consistency error occurred..

Hi all,
i have copied out the database backup from development center to my local machine,it is having approx.8GB in size and when
i m trying to restote this database backup in SQL Server 2000 it is showing me error.
An internal consistency error occurred. Contact Technical Support for assistance.
RESTORE DATABASE is terminating abnormally.
Plz. anyone can help me..

mukul:confused:Run RESTORE VERIFYONLY to ensure the backup is valid, and KBA http://support.microsoft.com/kb/268481 for further information. Try getting another set of backup to assure the source database server hardware is intact.|||Hi Satya,
i have run RESTORE VERIFYONLY command and after this is showing following msg-
Server: Msg 3242, Level 16, State 2, Line 1
The file on device 'g:\backup\projectServer\ProjectServer_db_20070709 0000.bak' is not a valid Microsoft Tape Format backup set.Server: Msg 3013, Level 16, State 1, Line 1
VERIFY DATABASE is terminating abnormally.
then what is this mean?
plz. help me out..

An existing connection was forcibly closed by the remote host

It is very appreciated if someone can help me on this problem:

I have 2 machines, connected with workgroup (not domain machine), 1 is win2003 sp1, 1 is xp.

How can I connect SSAS from XP machine with windows authentication?

Looks the Native client fix the windows authentication with local user name.

When I connect from XP, my application with following codes:

string connstr = "Provider=MSOLAP.3;Data Source=amsserver;Password=accenture;User ID=administrator;Initial Catalog=MIP2ASProject";

AdomdConnection objConnection = new AdomdConnection();

// Assign the connection string and try to

//open a connection.

objConnection.ConnectionString = connstr;

objConnection.Open();

It give me this error:

An existing connection was forcibly closed by the remote host

First of all, you dont need the User ID and Password in the connection string if you are connecting using TCP/IP (you would use them only when connecting with HTTP using Basic auth).

Second, in order to use "Provider=MSOLAP.3" you will need to install "Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB Provider" provider from http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi Edward,

Yes, I have installed oledb AS9 provider.

If you think SSAS only support windows authentication which must use inside the domain, I really couldn't understand why oledbconnection works fine with same connection string?

I am not sure about whether impersonation belong to windows authentication, but, my testing prove that oledb can connect in this way, adomd can't.

BTW, thankful if anyone can let me know how to enable SSAS's anonymous connection?

Jerry

|||

it is an antivirus problem

uninstall antivirus and try again

what antivirus do you have?

|||

What version of ADOM.NET are you using?

Try downloading and installing "Microsoft ADOMD.NET " from http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

An established connection was aborted by the software in your host machine.

I am getting connection errors all over the place, in everything I'm doing related to native client and connection issues failing with my database. I have changed users, authentification from windows to sql, everything. The latest was when I tried to apply the properties of my existing OLE DB Connection editor, one that has been working fine up until today. Every time I try to reselect the database and table in the properties if this, it errors out with the below:

TITLE: Microsoft SQL Native Client

Communication link failure
TCP Provider: An established connection was aborted by the software in your host machine.

BUTTONS:

&Retry
Cancel

Here are my logs:
http://www.photopizzaz.biz/junk/logs.txt
print screens of various errors I have received on my remote SQL Server 2005 (Enterprise version):
http://www.photopizzaz.biz/junk/sqlserver_2005_errors_and_resolutions.doc

Have you checked if remote connections are enabled for your server and what network protocols are available?

Please open SQL Server Surface Area Configuration tool and click 'Surface Area Configuraiton for Services and Connections' to set those settings.

An established connection was aborted by the software in your host machine.

I am getting connection errors all over the place, in everything I'm doing related to native client and connection issues failing with my database. I have changed users, authentification from windows to sql, everything. The latest was when I tried to apply the properties of my existing OLE DB Connection editor, one that has been working fine up until today. Every time I try to reselect the database and table in the properties if this, it errors out with the below:

TITLE: Microsoft SQL Native Client

Communication link failure
TCP Provider: An established connection was aborted by the software in your host machine.

BUTTONS:

&Retry
Cancel

Here are my logs:
http://www.photopizzaz.biz/junk/logs.txt
print screens of various errors I have received on my remote SQL Server 2005 (Enterprise version):
http://www.photopizzaz.biz/junk/sqlserver_2005_errors_and_resolutions.doc

Have you checked if remote connections are enabled for your server and what network protocols are available?

Please open SQL Server Surface Area Configuration tool and click 'Surface Area Configuraiton for Services and Connections' to set those settings.

An error occurred while established a connection

Hello

I am getting this err msg when trying to logon to my website on the web - on my machine there is no prob,

An error occurred while established a connection to the server.
When connection to Sql.S 2005, this failure may be caused by the fact that
under the default settings sql.s doesn't allow remote connection.
(provider ql.S Network interface, error:26- Error Location Server/Interface Specified)

(the files path is like in the web host s)

now this msg is related to the ASPNETDB.MDF (dont use sql.s db but this file)

thanks

Please check this blog for solutions:

http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx

|||

Do you have tcp/ip enabled on the server? If you connect from the local machine, you probably won't see the problem but when connecting from a remote machine, you will need tcp/ip enabled. Here are the steps from msdn:

Enable the TCP/IP protocol in SQL Server 2005. To do this, follow these steps:

1. Open SQL Server Configuration Manager. 2. Expand SQL Server 2005 Network Configuration. 3. Click Protocols for SQLInstanceName. SQLInstanceName is a placeholder for the name of the instance of SQL Server 2005. 4. Enable TCP/IP.

HTH

An error occurred while attempting to start the service (193)

I have seen several threads on this topic but none of the solutions
mentioned work for me. I recentley uninstalled MSSQL 200 from my
machine and now I am trying to reinstall. I get this message
consistently. Any help is appreciated.
Thanks!
12:17:31 C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINNT\sqlstp.log" -I
MSSQLSERVER -V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 66094 -U sa
-P
###############################################################################
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
An error occurred while attempting to start the service (193)
SQL Server configuration failed.
###############################################################################have you tried this kba?
http://support.microsoft.com/default.aspx?scid=kb;en-us;285100
"shcodip" wrote:
> I have seen several threads on this topic but none of the solutions
> mentioned work for me. I recentley uninstalled MSSQL 200 from my
> machine and now I am trying to reinstall. I get this message
> consistently. Any help is appreciated.
> Thanks!
> 12:17:31 C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINNT\sqlstp.log" -I
> MSSQLSERVER -V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 66094 -U sa
> -P
> ###############################################################################
>
> Starting Service ...
> SQL_Latin1_General_CP1_CI_AS
> -m -Q -T4022 -T3659
> An error occurred while attempting to start the service (193)
> SQL Server configuration failed.
> ###############################################################################
>|||My computer name is already upercase. So this does not apply.
Olu Adedeji wrote:
> have you tried this kba?
> http://support.microsoft.com/default.aspx?scid=kb;en-us;285100
> "shcodip" wrote:
> > I have seen several threads on this topic but none of the solutions
> > mentioned work for me. I recentley uninstalled MSSQL 200 from my
> > machine and now I am trying to reinstall. I get this message
> > consistently. Any help is appreciated.
> > Thanks!
> >
> > 12:17:31 C:\Program Files\Microsoft SQL
> > Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINNT\sqlstp.log" -I
> > MSSQLSERVER -V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 66094 -U
sa
> > -P
> >
###############################################################################
> >
> >
> > Starting Service ...
> >
> > SQL_Latin1_General_CP1_CI_AS
> >
> > -m -Q -T4022 -T3659
> >
> > An error occurred while attempting to start the service (193)
> >
> > SQL Server configuration failed.
> >
> >
###############################################################################
> >
> >

An error has occurred while establishing a connection to the server

Hi I have just reinstalled .Net and SqlServer2005. I am running my application from local machine and sqlserver is also install local machine. but when I run application. Get follwing Error Message

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

What was the application trying to do when you got this message? It may be that the connection string is not correct, it may be that the server is setup for only windows authentication.

|||

Hi

From your description, it seems that you met error when you are trying to connect to your SQLServer,right?

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

For this kind of issue, we should use the following steps to diagnose the problem.

First, you also should make sure that if 1433 port has been enabled on your server, which is the default port for SQLServer remote connections.

Generally, you can try the following ways to handle your problem.

1. Enable remote connections for SQL Server 2005 Express or SQL Server 2005 Developer Edition
2. Enable the SQL Server Browser service
3. Create exceptions in Windows Firewall
4. Create an exception for SQL Server 2005 in Windows Firewall
5. Create an exception for the SQL Server Browser service in Windows Firewall

More details for each step, you may see the following link:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277

Thanks.

An error about & quot;[dbnmpntw]ConnectionOpen(CreateFile())".

Hi:
When I tried to connect SQL Server Databse which was on another machine,
using Microsoft OLEDB Provider for SQL Server, error 0x80040005 was
returned, and the error message was
"& #91;dbnmpntw]ConnectionOpen(CreateFile()
)".Hi,
Use the SQL Client Configuration utility (from the machine u are connecting)
to create alias server name for the sql server using the TCP/IP protocol
specifying IP and port number.
And use this Alias name to connect to SQL server using TCP/IP
Thanks
Hari
MCDBA
"arxing" <cjx@.nbdx.cn> wrote in message
news:eAfe$8PWEHA.4092@.TK2MSFTNGP11.phx.gbl...
> Hi:
> When I tried to connect SQL Server Databse which was on another
machine,
> using Microsoft OLEDB Provider for SQL Server, error 0x80040005 was
> returned, and the error message was
> "& #91;dbnmpntw]ConnectionOpen(CreateFile()
)".
>|||But if I don't installed SQL Client on the machine I am connecting, what can
I do?
thanks.
"Hari" <hari_prasad_k@.hotmail.com> д?
news:elatIOQWEHA.1128@.TK2MSFTNGP10.phx.gbl...
> Hi,
> Use the SQL Client Configuration utility (from the machine u are
connecting)
> to create alias server name for the sql server using the TCP/IP protocol
> specifying IP and port number.
> And use this Alias name to connect to SQL server using TCP/IP
> --
> Thanks
> Hari
> MCDBA
> "arxing" <cjx@.nbdx.cn> wrote in message
> news:eAfe$8PWEHA.4092@.TK2MSFTNGP11.phx.gbl...
> machine,
>|||You can also do this using the wizard to set up an ODBC=20
data source. Use the Client Configuration button.

>--Original Message--
>But if I don't installed SQL Client on the machine I am=20
connecting, what can
>I do?
>thanks.
>
>"Hari" <hari_prasad_k@.hotmail.com> =D0=B4=C8=EB=D3=CA=BC=FE
>news:elatIOQWEHA.1128@.TK2MSFTNGP10.phx.gbl...
machine u are[vbcol=seagreen]
>connecting)
the TCP/IP protocol[vbcol=seagreen]
TCP/IP[vbcol=seagreen]
was on another[vbcol=seagreen]
0x80040005 was[vbcol=seagreen]
>
>.
>|||You can also do this when you set up the ODBC data source.=20
Use the Client Configuration button in the wizard.

>--Original Message--
>But if I don't installed SQL Client on the machine I am=20
connecting, what can
>I do?
>thanks.
>
>"Hari" <hari_prasad_k@.hotmail.com> =D0=B4=C8=EB=D3=CA=BC=FE
>news:elatIOQWEHA.1128@.TK2MSFTNGP10.phx.gbl...
machine u are[vbcol=seagreen]
>connecting)
the TCP/IP protocol[vbcol=seagreen]
TCP/IP[vbcol=seagreen]
was on another[vbcol=seagreen]
0x80040005 was[vbcol=seagreen]
>
>.
>|||This utility is available even if you didn't install the SQL Client tools -
start -> run -> Cliconfg.exe.
Richard Waymire, MCSE, MCDBA
This posting is provided "AS IS" with no warranties, and confers no rights.
"arxing" <cjx@.nbdx.cn> wrote in message
news:O3sk4WSWEHA.4048@.TK2MSFTNGP12.phx.gbl...
> But if I don't installed SQL Client on the machine I am connecting, what
> can
> I do?
> thanks.
>
> "Hari" <hari_prasad_k@.hotmail.com> д?
> news:elatIOQWEHA.1128@.TK2MSFTNGP10.phx.gbl...
> connecting)
>

Am I really using the full 2GB of Ram?

We have a machine Server2000 / SQL Standard 2000.
This machine has 2.5GB of RAM, but when we go into Task Manager we see
the SqlServr.exe process is only using 1,740,000 KB of memory.
This comes out to about 1.65 GB.
I have heard that this might actually be the max amount of memory that
will be consumed. In other words, have we really reached our max
memory allowed by SQL Server 2000 Standard?
Also, we are thinking about what we can do to allow us to take
advantage of over 2GB. Is it correct that we a) Must have SQL Server
Enterprise 2000 and b) must run on Windows 2000 Advanced Server or 2003
Datacenter edition?
THANKS!
cmay,
SQL Server will only take as much RAM as it needs, and generally will
not release it unless asked for by the OS.
If you want to use more than 2Gb RAM for SQL Server you will need
Enterprise Edition.
Check out:
http://www.microsoft.com/sql/techinf...sKChooseEd.asp
and
http://www.microsoft.com/sql/evaluat...ew/default.asp
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
cmay wrote:
> We have a machine Server2000 / SQL Standard 2000.
> This machine has 2.5GB of RAM, but when we go into Task Manager we see
> the SqlServr.exe process is only using 1,740,000 KB of memory.
> This comes out to about 1.65 GB.
> I have heard that this might actually be the max amount of memory that
> will be consumed. In other words, have we really reached our max
> memory allowed by SQL Server 2000 Standard?
> Also, we are thinking about what we can do to allow us to take
> advantage of over 2GB. Is it correct that we a) Must have SQL Server
> Enterprise 2000 and b) must run on Windows 2000 Advanced Server or 2003
> Datacenter edition?
>
> THANKS!
>
|||Mark,
Thanks for the reply.
I basically have 2 follow up questions:
1) If a computer running 2000 Standard has maxed out its 2GB of
memory, will it actually show up as 2GB of memory under the
SQLServr.exe process in task manager? Some have suggested that our
1,740,000 KB (about) is really the max that SQL Server Standard will
consume, even though it only adds up to about 1.65GB of RAM.
2) Can Enterprise edition make use of over 2GB of Ram while running on
Windows 2000 Server, or must it run on W2k Advanced Server / Datacenter
edition? I have read lots of stuff that says you *can* install SQL
Enterprise on W2k Server, but I also read that in order to use over
2GB, it must use AWE, which is only available on Advanced Server /
Datacenter editions of windows.
Can you clarify this?
|||"cmay" <cmay@.walshgroup.com> wrote in message
news:1118848547.194627.53370@.o13g2000cwo.googlegro ups.com...
> We have a machine Server2000 / SQL Standard 2000.
> This machine has 2.5GB of RAM, but when we go into Task Manager we see
> the SqlServr.exe process is only using 1,740,000 KB of memory.
> This comes out to about 1.65 GB.
> I have heard that this might actually be the max amount of memory that
> will be consumed.
This is likely. Depending on your configuration.

> In other words, have we really reached our max
> memory allowed by SQL Server 2000 Standard?
Try pinning this memory if you want the process to take the full 2GBs.
USE master
EXEC sp_configure 'show advanced option', '1'
RECONFIGURE
EXEC sp_configure 'max server memory', '2048'
RECONFIGURE
EXEC sp_configure 'min server memory', '2048'
RECONFIGURE
EXEC sp_configure 'set working set size', '1'
RECONFIGURE

> Also, we are thinking about what we can do to allow us to take
> advantage of over 2GB. Is it correct that we a) Must have SQL Server
> Enterprise 2000 and b) must run on Windows 2000 Advanced Server or 2003
> Datacenter edition?
You will need SQL Server and Windows Server editions that are beyond the
"Standard" editions.
http://support.microsoft.com/default...b;en-us;274750
...
|||Hi
SQL Server needs to leave about 256Mb or RAM in the MemToLeave area. This
allows for SQL Agent, XP's etc to run. With 2GB, the maximum SQL Server will
show is 1.65Gb.
Standard Windows 2000 supports up to 4GB or RAM. If you were to install SQL
server Enterprise Edition, it could use 3GB as the other 1GB is reserved for
the OS under Windows 32 bit.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"cmay" <cmay@.walshgroup.com> wrote in message
news:1118854442.903913.82200@.g47g2000cwa.googlegro ups.com...
> Mark,
>
> Thanks for the reply.
> I basically have 2 follow up questions:
> 1) If a computer running 2000 Standard has maxed out its 2GB of
> memory, will it actually show up as 2GB of memory under the
> SQLServr.exe process in task manager? Some have suggested that our
> 1,740,000 KB (about) is really the max that SQL Server Standard will
> consume, even though it only adds up to about 1.65GB of RAM.
> 2) Can Enterprise edition make use of over 2GB of Ram while running on
> Windows 2000 Server, or must it run on W2k Advanced Server / Datacenter
> edition? I have read lots of stuff that says you *can* install SQL
> Enterprise on W2k Server, but I also read that in order to use over
> 2GB, it must use AWE, which is only available on Advanced Server /
> Datacenter editions of windows.
> Can you clarify this?
>
|||Thanks Mike

Am I really using the full 2GB of Ram?

We have a machine Server2000 / SQL Standard 2000.
This machine has 2.5GB of RAM, but when we go into Task Manager we see
the SqlServr.exe process is only using 1,740,000 KB of memory.
This comes out to about 1.65 GB.
I have heard that this might actually be the max amount of memory that
will be consumed. In other words, have we really reached our max
memory allowed by SQL Server 2000 Standard?
Also, we are thinking about what we can do to allow us to take
advantage of over 2GB. Is it correct that we a) Must have SQL Server
Enterprise 2000 and b) must run on Windows 2000 Advanced Server or 2003
Datacenter edition?
THANKS!cmay,
SQL Server will only take as much RAM as it needs, and generally will
not release it unless asked for by the OS.
If you want to use more than 2Gb RAM for SQL Server you will need
Enterprise Edition.
Check out:
http://www.microsoft.com/sql/techinfo/planning/SQLResKChooseEd.asp
and
http://www.microsoft.com/sql/evaluation/overview/default.asp
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
cmay wrote:
> We have a machine Server2000 / SQL Standard 2000.
> This machine has 2.5GB of RAM, but when we go into Task Manager we see
> the SqlServr.exe process is only using 1,740,000 KB of memory.
> This comes out to about 1.65 GB.
> I have heard that this might actually be the max amount of memory that
> will be consumed. In other words, have we really reached our max
> memory allowed by SQL Server 2000 Standard?
> Also, we are thinking about what we can do to allow us to take
> advantage of over 2GB. Is it correct that we a) Must have SQL Server
> Enterprise 2000 and b) must run on Windows 2000 Advanced Server or 2003
> Datacenter edition?
>
> THANKS!
>|||Mark,
Thanks for the reply.
I basically have 2 follow up questions:
1) If a computer running 2000 Standard has maxed out its 2GB of
memory, will it actually show up as 2GB of memory under the
SQLServr.exe process in task manager? Some have suggested that our
1,740,000 KB (about) is really the max that SQL Server Standard will
consume, even though it only adds up to about 1.65GB of RAM.
2) Can Enterprise edition make use of over 2GB of Ram while running on
Windows 2000 Server, or must it run on W2k Advanced Server / Datacenter
edition? I have read lots of stuff that says you *can* install SQL
Enterprise on W2k Server, but I also read that in order to use over
2GB, it must use AWE, which is only available on Advanced Server /
Datacenter editions of windows.
Can you clarify this?|||"cmay" <cmay@.walshgroup.com> wrote in message
news:1118848547.194627.53370@.o13g2000cwo.googlegroups.com...
> We have a machine Server2000 / SQL Standard 2000.
> This machine has 2.5GB of RAM, but when we go into Task Manager we see
> the SqlServr.exe process is only using 1,740,000 KB of memory.
> This comes out to about 1.65 GB.
> I have heard that this might actually be the max amount of memory that
> will be consumed.
This is likely. Depending on your configuration.
> In other words, have we really reached our max
> memory allowed by SQL Server 2000 Standard?
Try pinning this memory if you want the process to take the full 2GBs.
USE master
EXEC sp_configure 'show advanced option', '1'
RECONFIGURE
EXEC sp_configure 'max server memory', '2048'
RECONFIGURE
EXEC sp_configure 'min server memory', '2048'
RECONFIGURE
EXEC sp_configure 'set working set size', '1'
RECONFIGURE
> Also, we are thinking about what we can do to allow us to take
> advantage of over 2GB. Is it correct that we a) Must have SQL Server
> Enterprise 2000 and b) must run on Windows 2000 Advanced Server or 2003
> Datacenter edition?
You will need SQL Server and Windows Server editions that are beyond the
"Standard" editions.
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
...|||Hi
SQL Server needs to leave about 256Mb or RAM in the MemToLeave area. This
allows for SQL Agent, XP's etc to run. With 2GB, the maximum SQL Server will
show is 1.65Gb.
Standard Windows 2000 supports up to 4GB or RAM. If you were to install SQL
server Enterprise Edition, it could use 3GB as the other 1GB is reserved for
the OS under Windows 32 bit.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"cmay" <cmay@.walshgroup.com> wrote in message
news:1118854442.903913.82200@.g47g2000cwa.googlegroups.com...
> Mark,
>
> Thanks for the reply.
> I basically have 2 follow up questions:
> 1) If a computer running 2000 Standard has maxed out its 2GB of
> memory, will it actually show up as 2GB of memory under the
> SQLServr.exe process in task manager? Some have suggested that our
> 1,740,000 KB (about) is really the max that SQL Server Standard will
> consume, even though it only adds up to about 1.65GB of RAM.
> 2) Can Enterprise edition make use of over 2GB of Ram while running on
> Windows 2000 Server, or must it run on W2k Advanced Server / Datacenter
> edition? I have read lots of stuff that says you *can* install SQL
> Enterprise on W2k Server, but I also read that in order to use over
> 2GB, it must use AWE, which is only available on Advanced Server /
> Datacenter editions of windows.
> Can you clarify this?
>|||Thanks Mike

Am I really using the full 2GB of Ram?

We have a machine Server2000 / SQL Standard 2000.
This machine has 2.5GB of RAM, but when we go into Task Manager we see
the SqlServr.exe process is only using 1,740,000 KB of memory.
This comes out to about 1.65 GB.
I have heard that this might actually be the max amount of memory that
will be consumed. In other words, have we really reached our max
memory allowed by SQL Server 2000 Standard?
Also, we are thinking about what we can do to allow us to take
advantage of over 2GB. Is it correct that we a) Must have SQL Server
Enterprise 2000 and b) must run on Windows 2000 Advanced Server or 2003
Datacenter edition?
THANKS!cmay,
SQL Server will only take as much RAM as it needs, and generally will
not release it unless asked for by the OS.
If you want to use more than 2Gb RAM for SQL Server you will need
Enterprise Edition.
Check out:
http://www.microsoft.com/sql/techin...esKChooseEd.asp
and
http://www.microsoft.com/sql/evalua...iew/default.asp
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
cmay wrote:
> We have a machine Server2000 / SQL Standard 2000.
> This machine has 2.5GB of RAM, but when we go into Task Manager we see
> the SqlServr.exe process is only using 1,740,000 KB of memory.
> This comes out to about 1.65 GB.
> I have heard that this might actually be the max amount of memory that
> will be consumed. In other words, have we really reached our max
> memory allowed by SQL Server 2000 Standard?
> Also, we are thinking about what we can do to allow us to take
> advantage of over 2GB. Is it correct that we a) Must have SQL Server
> Enterprise 2000 and b) must run on Windows 2000 Advanced Server or 2003
> Datacenter edition?
>
> THANKS!
>|||Mark,
Thanks for the reply.
I basically have 2 follow up questions:
1) If a computer running 2000 Standard has maxed out its 2GB of
memory, will it actually show up as 2GB of memory under the
SQLServr.exe process in task manager? Some have suggested that our
1,740,000 KB (about) is really the max that SQL Server Standard will
consume, even though it only adds up to about 1.65GB of RAM.
2) Can Enterprise edition make use of over 2GB of Ram while running on
Windows 2000 Server, or must it run on W2k Advanced Server / Datacenter
edition? I have read lots of stuff that says you *can* install SQL
Enterprise on W2k Server, but I also read that in order to use over
2GB, it must use AWE, which is only available on Advanced Server /
Datacenter editions of windows.
Can you clarify this?|||"cmay" <cmay@.walshgroup.com> wrote in message
news:1118848547.194627.53370@.o13g2000cwo.googlegroups.com...
> We have a machine Server2000 / SQL Standard 2000.
> This machine has 2.5GB of RAM, but when we go into Task Manager we see
> the SqlServr.exe process is only using 1,740,000 KB of memory.
> This comes out to about 1.65 GB.
> I have heard that this might actually be the max amount of memory that
> will be consumed.
This is likely. Depending on your configuration.

> In other words, have we really reached our max
> memory allowed by SQL Server 2000 Standard?
Try pinning this memory if you want the process to take the full 2GBs.
USE master
EXEC sp_configure 'show advanced option', '1'
RECONFIGURE
EXEC sp_configure 'max server memory', '2048'
RECONFIGURE
EXEC sp_configure 'min server memory', '2048'
RECONFIGURE
EXEC sp_configure 'set working set size', '1'
RECONFIGURE

> Also, we are thinking about what we can do to allow us to take
> advantage of over 2GB. Is it correct that we a) Must have SQL Server
> Enterprise 2000 and b) must run on Windows 2000 Advanced Server or 2003
> Datacenter edition?
You will need SQL Server and Windows Server editions that are beyond the
"Standard" editions.
http://support.microsoft.com/defaul...kb;en-us;274750
...|||Hi
SQL Server needs to leave about 256Mb or RAM in the MemToLeave area. This
allows for SQL Agent, XP's etc to run. With 2GB, the maximum SQL Server will
show is 1.65Gb.
Standard Windows 2000 supports up to 4GB or RAM. If you were to install SQL
server Enterprise Edition, it could use 3GB as the other 1GB is reserved for
the OS under Windows 32 bit.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"cmay" <cmay@.walshgroup.com> wrote in message
news:1118854442.903913.82200@.g47g2000cwa.googlegroups.com...
> Mark,
>
> Thanks for the reply.
> I basically have 2 follow up questions:
> 1) If a computer running 2000 Standard has maxed out its 2GB of
> memory, will it actually show up as 2GB of memory under the
> SQLServr.exe process in task manager? Some have suggested that our
> 1,740,000 KB (about) is really the max that SQL Server Standard will
> consume, even though it only adds up to about 1.65GB of RAM.
> 2) Can Enterprise edition make use of over 2GB of Ram while running on
> Windows 2000 Server, or must it run on W2k Advanced Server / Datacenter
> edition? I have read lots of stuff that says you *can* install SQL
> Enterprise on W2k Server, but I also read that in order to use over
> 2GB, it must use AWE, which is only available on Advanced Server /
> Datacenter editions of windows.
> Can you clarify this?
>|||Thanks Mike

Always write to Windows event log" doesn't work in MS SQL Server 2

Hi,
I have an MS SQL Server 2000 SP3, MS Windows 2000 SP4 machine. When I set
the "Always write to Windows event log" option for the 14150 (replication
agent success) error and start a snapshot agent, a message is logged in SQL
Server errorlog but not in Windows application log. Why?
-- Thanks, Oskar.
Sorry this wasn't a valid question. The error actually is logged, only it is
logged as an informational message, not error message. I was mislead by that.
--Thanks, Oskar.
"Oskar" wrote:

> Hi,
> I have an MS SQL Server 2000 SP3, MS Windows 2000 SP4 machine. When I set
> the "Always write to Windows event log" option for the 14150 (replication
> agent success) error and start a snapshot agent, a message is logged in SQL
> Server errorlog but not in Windows application log. Why?
> -- Thanks, Oskar.
>

Always write to Windows event log" doesn't work in MS SQL Server 2

Hi,
I have an MS SQL Server 2000 SP3, MS Windows 2000 SP4 machine. When I set
the "Always write to Windows event log" option for the 14150 (replication
agent success) error and start a snapshot agent, a message is logged in SQL
Server errorlog but not in Windows application log. Why?
-- Thanks, Oskar.Sorry this wasn't a valid question. The error actually is logged, only it is
logged as an informational message, not error message. I was mislead by that
.
--Thanks, Oskar.
"Oskar" wrote:

> Hi,
> I have an MS SQL Server 2000 SP3, MS Windows 2000 SP4 machine. When I set
> the "Always write to Windows event log" option for the 14150 (replication
> agent success) error and start a snapshot agent, a message is logged in SQ
L
> Server errorlog but not in Windows application log. Why?
> -- Thanks, Oskar.
>

Always write to Windows event log" doesn't work in MS SQL Server 2

Hi,
I have an MS SQL Server 2000 SP3, MS Windows 2000 SP4 machine. When I set
the "Always write to Windows event log" option for the 14150 (replication
agent success) error and start a snapshot agent, a message is logged in SQL
Server errorlog but not in Windows application log. Why?
-- Thanks, Oskar.Sorry this wasn't a valid question. The error actually is logged, only it is
logged as an informational message, not error message. I was mislead by that.
--Thanks, Oskar.
"Oskar" wrote:
> Hi,
> I have an MS SQL Server 2000 SP3, MS Windows 2000 SP4 machine. When I set
> the "Always write to Windows event log" option for the 14150 (replication
> agent success) error and start a snapshot agent, a message is logged in SQL
> Server errorlog but not in Windows application log. Why?
> -- Thanks, Oskar.
>

Alternative to xp_sendmail on 64 Bit SQL Server 2000

I'm looking for any alternative methods that can be used in place of the
xp_sendmail extended stored procedure when running on a 64 bit machine with
the 64 bit version of SQL Server 2000.
Any proven suggestions would be extremely helpful.
Not sure if this can help:
http://www.sqldev.net/xp/xpsmtp.htm
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
"Gordon Radley" <GordonRadley@.discussions.microsoft.com> wrote in message
news:DF298AAC-3340-47E4-BFA4-5006512B070D@.microsoft.com...
> I'm looking for any alternative methods that can be used in place of the
> xp_sendmail extended stored procedure when running on a 64 bit machine
> with
> the 64 bit version of SQL Server 2000.
> Any proven suggestions would be extremely helpful.
|||xp_smtp_sendmail doesn't work (probably because it's compiled for win32).
If anybody find a solution please tell me too.
"Gordon Radley" <GordonRadley@.discussions.microsoft.com> wrote in message
news:DF298AAC-3340-47E4-BFA4-5006512B070D@.microsoft.com...
> I'm looking for any alternative methods that can be used in place of the
> xp_sendmail extended stored procedure when running on a 64 bit machine
> with
> the 64 bit version of SQL Server 2000.
> Any proven suggestions would be extremely helpful.