The easiest way of doing it is to go onto your server,
doing a CTR ALT DEL, bringing up task manager, then
looking for SQL Server under the processors list.
Peter
"I'm just preparing my impromptu remarks."
Winston Churchill
>--Original Message--
>I've been doing a lot of reading on this and my head is
starting to
>hurt! It seems to be quite a feat to work out how much
memory is
>actually being used by our server.
>I'm running W2K advanced server with SQL 2000 EE, 8GB of
RAM, a min of
>4GB and a max of 6GB is assigned to SQL server.
>I'm trying to work out whether we've assigned enough or
too
>much/little memory to SQL server. My first thought was to
let SQL
>dymanically manage its own memory and see how much it
uses, of course
>when AWE (/3GB /PAE) is enabled it will just use all that
is
>available.
>In perfmon "target server memory" = 6.1GB, "total server
memory" =
>6.1GB, "total pages" = 768000 ( x 8KB = 6.1GB).
>My second thought was to use "total pages" - the
average "free pages"
>= average mem used, therefore giving me the average
amount of memory
>used by SQL. I found out that SQL uses a min of 4GB (the
min we
>assigned) and the max of all the memory, 6GB.
>Is there an easier way of finding out how much memory is
actually used
>in this situation or is going by the above average the
best way?
>What i'm unsure about is if, for example, we made 1TB of
RAM
>available, will SQL just use all memory assigned to it
until it has
>the whole DB in memory? If not, what's the cut off? Or is
the fact
>that the memory usage of our instance of sql peaks at
using all the
>memory an indication that we do not have enough available?
>Any help would be greatly apprechiated.
>Thanks.
>.
>
I don't know if that method will work.
We are running SQL 2k EE on Win2k AS. We are using /3GB /PAE and SQL Server
is configured to use 6144 MB.
Task manager reports that sqlservr.exe is using 115,524K on the process tab
however on the performance tab the physical memory is reported as
Total 7863624
Available 1184100
Keith
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:15d501c4bc26$57a92ae0$a601280a@.phx.gbl...[vbcol=seagreen]
> The easiest way of doing it is to go onto your server,
> doing a CTR ALT DEL, bringing up task manager, then
> looking for SQL Server under the processors list.
> Peter
> "I'm just preparing my impromptu remarks."
> Winston Churchill
>
> starting to
> memory is
> RAM, a min of
> too
> let SQL
> uses, of course
> is
> memory" =
> average "free pages"
> amount of memory
> min we
> actually used
> best way?
> RAM
> until it has
> the fact
> using all the
|||Keith,
I think you have a point there.
However Task Manager will always show the amount of memory
that has been allocated to a process, and is very accurate
(as far as I know)
I suppose the question(s) is more of
1. How much memory has been allocated
2. How much of that memory is in use
3. How much more memory can be accessed
Anyway as it piked my interest I dug out my copy of
Performance Monitoring with SQL Server 2000 and set up the
counters Total Server Memory and Target Server Memory.
As you know it will show percentage of the actual memory
useage on the server.
Currently our server is set to 48% of all server memory,
which translates roughly to the amount of memory shown as
used in Task Manager, though I will freely admit its not
completely accurate.
I think the answer then is there is no way of totally been
able to predict the amount of memory being used, as both
things give different figures.
So I think I will change my mind and go down your route
using the profiler if nothing more than the fact you take
the findings at a regular time and do something with them.
Anyway thanks for that.
Peter
"Action speaks louder than words but not nearly as often"
Mark Twain
>--Original Message--
>I don't know if that method will work.
>We are running SQL 2k EE on Win2k AS. We are
using /3GB /PAE and SQL Server
>is configured to use 6144 MB.
>Task manager reports that sqlservr.exe is using 115,524K
on the process tab
>however on the performance tab the physical memory is
reported as
>Total 7863624
>Available 1184100
>--
>Keith
>
>"Peter The Spate" <anonymous@.discussions.microsoft.com>
wrote in message[vbcol=seagreen]
>news:15d501c4bc26$57a92ae0$a601280a@.phx.gbl...
of[vbcol=seagreen]
to[vbcol=seagreen]
that[vbcol=seagreen]
server[vbcol=seagreen]
(the[vbcol=seagreen]
is[vbcol=seagreen]
of[vbcol=seagreen]
is[vbcol=seagreen]
available?
>.
>
|||Spot on. Windows counters such as these in task manager and process
and working set in perfmon cannot monitor memory that is enabled by
AWE, 4GB+. I wish it were that easy.
In my situation, because the min and max memory is set to 4GB and 6GB
none of this can be monitored by the usual tools, it's all AWE memory.
What i need to know is;
-Should i be concerned that SQL memory usage peaks at using all memory
assigned to it?
-Should it peak at 100% mem usage, is this normal?
-If i assigned, for example, 40GB of memory would it just keep using
memory until it had the hole db in memory (20gb db).
-If that's not the case when does it stop using memory?
Your thoughts,
Thanks.
|||comments inline
Keith
"Tim Richardson" <tim@.specialmail.co.uk> wrote in message
news:25879432.0410280128.5080316a@.posting.google.c om...
> Spot on. Windows counters such as these in task manager and process
> and working set in perfmon cannot monitor memory that is enabled by
> AWE, 4GB+. I wish it were that easy.
> In my situation, because the min and max memory is set to 4GB and 6GB
> none of this can be monitored by the usual tools, it's all AWE memory.
> What i need to know is;
> -Should i be concerned that SQL memory usage peaks at using all memory
> assigned to it?
No
> -Should it peak at 100% mem usage, is this normal?
Yes
INF: SQL Server Memory Usage
http://support.microsoft.com/default...;en-us;q321363
> -If i assigned, for example, 40GB of memory would it just keep using
> memory until it had the hole db in memory (20gb db).
It might use slightly more RAM [than 20GB] because it would (could) have
data and query plans in cache. It might also decide that it wants
additional memory for SQL Agent, user connections, and so on.
> -If that's not the case when does it stop using memory?
When it does not need any more.
> Your thoughts,
> Thanks.
Showing posts with label manager. Show all posts
Showing posts with label manager. Show all posts
Monday, March 19, 2012
How to tell how much memory is actually needed by my SQL Server 2000?
The easiest way of doing it is to go onto your server,
doing a CTR ALT DEL, bringing up task manager, then
looking for SQL Server under the processors list.
Peter
"I'm just preparing my impromptu remarks."
Winston Churchill
>--Original Message--
>I've been doing a lot of reading on this and my head is
starting to
>hurt! It seems to be quite a feat to work out how much
memory is
>actually being used by our server.
>I'm running W2K advanced server with SQL 2000 EE, 8GB of
RAM, a min of
>4GB and a max of 6GB is assigned to SQL server.
>I'm trying to work out whether we've assigned enough or
too
>much/little memory to SQL server. My first thought was to
let SQL
>dymanically manage its own memory and see how much it
uses, of course
>when AWE (/3GB /PAE) is enabled it will just use all that
is
>available.
>In perfmon "target server memory" = 6.1GB, "total server
memory" =
>6.1GB, "total pages" = 768000 ( x 8KB = 6.1GB).
>My second thought was to use "total pages" - the
average "free pages"
>= average mem used, therefore giving me the average
amount of memory
>used by SQL. I found out that SQL uses a min of 4GB (the
min we
>assigned) and the max of all the memory, 6GB.
>Is there an easier way of finding out how much memory is
actually used
>in this situation or is going by the above average the
best way?
>What i'm unsure about is if, for example, we made 1TB of
RAM
>available, will SQL just use all memory assigned to it
until it has
>the whole DB in memory? If not, what's the cut off? Or is
the fact
>that the memory usage of our instance of sql peaks at
using all the
>memory an indication that we do not have enough available?
>Any help would be greatly apprechiated.
>Thanks.
>.
>I don't know if that method will work.
We are running SQL 2k EE on Win2k AS. We are using /3GB /PAE and SQL Server
is configured to use 6144 MB.
Task manager reports that sqlservr.exe is using 115,524K on the process tab
however on the performance tab the physical memory is reported as
Total 7863624
Available 1184100
Keith
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:15d501c4bc26$57a92ae0$a601280a@.phx.gbl...[vbcol=seagreen]
> The easiest way of doing it is to go onto your server,
> doing a CTR ALT DEL, bringing up task manager, then
> looking for SQL Server under the processors list.
> Peter
> "I'm just preparing my impromptu remarks."
> Winston Churchill
>
>
> starting to
> memory is
> RAM, a min of
> too
> let SQL
> uses, of course
> is
> memory" =
> average "free pages"
> amount of memory
> min we
> actually used
> best way?
> RAM
> until it has
> the fact
> using all the|||Keith,
I think you have a point there.
However Task Manager will always show the amount of memory
that has been allocated to a process, and is very accurate
(as far as I know)
I suppose the question(s) is more of
1. How much memory has been allocated
2. How much of that memory is in use
3. How much more memory can be accessed
Anyway as it piked my interest I dug out my copy of
Performance Monitoring with SQL Server 2000 and set up the
counters Total Server Memory and Target Server Memory.
As you know it will show percentage of the actual memory
useage on the server.
Currently our server is set to 48% of all server memory,
which translates roughly to the amount of memory shown as
used in Task Manager, though I will freely admit its not
completely accurate.
I think the answer then is there is no way of totally been
able to predict the amount of memory being used, as both
things give different figures.
So I think I will change my mind and go down your route
using the profiler if nothing more than the fact you take
the findings at a regular time and do something with them.
Anyway thanks for that.
Peter
"Action speaks louder than words but not nearly as often"
Mark Twain
>--Original Message--
>I don't know if that method will work.
>We are running SQL 2k EE on Win2k AS. We are
using /3GB /PAE and SQL Server
>is configured to use 6144 MB.
>Task manager reports that sqlservr.exe is using 115,524K
on the process tab
>however on the performance tab the physical memory is
reported as
>Total 7863624
>Available 1184100
>--
>Keith
>
>"Peter The Spate" <anonymous@.discussions.microsoft.com>
wrote in message
>news:15d501c4bc26$57a92ae0$a601280a@.phx.gbl...
of[vbcol=seagreen]
to[vbcol=seagreen]
that[vbcol=seagreen]
server[vbcol=seagreen]
(the[vbcol=seagreen]
is[vbcol=seagreen]
of[vbcol=seagreen]
is[vbcol=seagreen]
available?[vbcol=seagreen]
>.
>|||Spot on. Windows counters such as these in task manager and process
and working set in perfmon cannot monitor memory that is enabled by
AWE, 4GB+. I wish it were that easy.
In my situation, because the min and max memory is set to 4GB and 6GB
none of this can be monitored by the usual tools, it's all AWE memory.
What i need to know is;
-Should i be concerned that SQL memory usage peaks at using all memory
assigned to it?
-Should it peak at 100% mem usage, is this normal?
-If i assigned, for example, 40GB of memory would it just keep using
memory until it had the hole db in memory (20gb db).
-If that's not the case when does it stop using memory?
Your thoughts,
Thanks.|||comments inline
Keith
"Tim Richardson" <tim@.specialmail.co.uk> wrote in message
news:25879432.0410280128.5080316a@.posting.google.com...
> Spot on. Windows counters such as these in task manager and process
> and working set in perfmon cannot monitor memory that is enabled by
> AWE, 4GB+. I wish it were that easy.
> In my situation, because the min and max memory is set to 4GB and 6GB
> none of this can be monitored by the usual tools, it's all AWE memory.
> What i need to know is;
> -Should i be concerned that SQL memory usage peaks at using all memory
> assigned to it?
No
> -Should it peak at 100% mem usage, is this normal?
Yes
INF: SQL Server Memory Usage
http://support.microsoft.com/defaul...b;en-us;q321363
> -If i assigned, for example, 40GB of memory would it just keep using
> memory until it had the hole db in memory (20gb db).
It might use slightly more RAM [than 20GB] because it would (could) have
data and query plans in cache. It might also decide that it wants
additional memory for SQL Agent, user connections, and so on.
> -If that's not the case when does it stop using memory?
When it does not need any more.
> Your thoughts,
> Thanks.
doing a CTR ALT DEL, bringing up task manager, then
looking for SQL Server under the processors list.
Peter
"I'm just preparing my impromptu remarks."
Winston Churchill
>--Original Message--
>I've been doing a lot of reading on this and my head is
starting to
>hurt! It seems to be quite a feat to work out how much
memory is
>actually being used by our server.
>I'm running W2K advanced server with SQL 2000 EE, 8GB of
RAM, a min of
>4GB and a max of 6GB is assigned to SQL server.
>I'm trying to work out whether we've assigned enough or
too
>much/little memory to SQL server. My first thought was to
let SQL
>dymanically manage its own memory and see how much it
uses, of course
>when AWE (/3GB /PAE) is enabled it will just use all that
is
>available.
>In perfmon "target server memory" = 6.1GB, "total server
memory" =
>6.1GB, "total pages" = 768000 ( x 8KB = 6.1GB).
>My second thought was to use "total pages" - the
average "free pages"
>= average mem used, therefore giving me the average
amount of memory
>used by SQL. I found out that SQL uses a min of 4GB (the
min we
>assigned) and the max of all the memory, 6GB.
>Is there an easier way of finding out how much memory is
actually used
>in this situation or is going by the above average the
best way?
>What i'm unsure about is if, for example, we made 1TB of
RAM
>available, will SQL just use all memory assigned to it
until it has
>the whole DB in memory? If not, what's the cut off? Or is
the fact
>that the memory usage of our instance of sql peaks at
using all the
>memory an indication that we do not have enough available?
>Any help would be greatly apprechiated.
>Thanks.
>.
>I don't know if that method will work.
We are running SQL 2k EE on Win2k AS. We are using /3GB /PAE and SQL Server
is configured to use 6144 MB.
Task manager reports that sqlservr.exe is using 115,524K on the process tab
however on the performance tab the physical memory is reported as
Total 7863624
Available 1184100
Keith
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:15d501c4bc26$57a92ae0$a601280a@.phx.gbl...[vbcol=seagreen]
> The easiest way of doing it is to go onto your server,
> doing a CTR ALT DEL, bringing up task manager, then
> looking for SQL Server under the processors list.
> Peter
> "I'm just preparing my impromptu remarks."
> Winston Churchill
>
>
> starting to
> memory is
> RAM, a min of
> too
> let SQL
> uses, of course
> is
> memory" =
> average "free pages"
> amount of memory
> min we
> actually used
> best way?
> RAM
> until it has
> the fact
> using all the|||Keith,
I think you have a point there.
However Task Manager will always show the amount of memory
that has been allocated to a process, and is very accurate
(as far as I know)
I suppose the question(s) is more of
1. How much memory has been allocated
2. How much of that memory is in use
3. How much more memory can be accessed
Anyway as it piked my interest I dug out my copy of
Performance Monitoring with SQL Server 2000 and set up the
counters Total Server Memory and Target Server Memory.
As you know it will show percentage of the actual memory
useage on the server.
Currently our server is set to 48% of all server memory,
which translates roughly to the amount of memory shown as
used in Task Manager, though I will freely admit its not
completely accurate.
I think the answer then is there is no way of totally been
able to predict the amount of memory being used, as both
things give different figures.
So I think I will change my mind and go down your route
using the profiler if nothing more than the fact you take
the findings at a regular time and do something with them.
Anyway thanks for that.
Peter
"Action speaks louder than words but not nearly as often"
Mark Twain
>--Original Message--
>I don't know if that method will work.
>We are running SQL 2k EE on Win2k AS. We are
using /3GB /PAE and SQL Server
>is configured to use 6144 MB.
>Task manager reports that sqlservr.exe is using 115,524K
on the process tab
>however on the performance tab the physical memory is
reported as
>Total 7863624
>Available 1184100
>--
>Keith
>
>"Peter The Spate" <anonymous@.discussions.microsoft.com>
wrote in message
>news:15d501c4bc26$57a92ae0$a601280a@.phx.gbl...
of[vbcol=seagreen]
to[vbcol=seagreen]
that[vbcol=seagreen]
server[vbcol=seagreen]
(the[vbcol=seagreen]
is[vbcol=seagreen]
of[vbcol=seagreen]
is[vbcol=seagreen]
available?[vbcol=seagreen]
>.
>|||Spot on. Windows counters such as these in task manager and process
and working set in perfmon cannot monitor memory that is enabled by
AWE, 4GB+. I wish it were that easy.
In my situation, because the min and max memory is set to 4GB and 6GB
none of this can be monitored by the usual tools, it's all AWE memory.
What i need to know is;
-Should i be concerned that SQL memory usage peaks at using all memory
assigned to it?
-Should it peak at 100% mem usage, is this normal?
-If i assigned, for example, 40GB of memory would it just keep using
memory until it had the hole db in memory (20gb db).
-If that's not the case when does it stop using memory?
Your thoughts,
Thanks.|||comments inline
Keith
"Tim Richardson" <tim@.specialmail.co.uk> wrote in message
news:25879432.0410280128.5080316a@.posting.google.com...
> Spot on. Windows counters such as these in task manager and process
> and working set in perfmon cannot monitor memory that is enabled by
> AWE, 4GB+. I wish it were that easy.
> In my situation, because the min and max memory is set to 4GB and 6GB
> none of this can be monitored by the usual tools, it's all AWE memory.
> What i need to know is;
> -Should i be concerned that SQL memory usage peaks at using all memory
> assigned to it?
No
> -Should it peak at 100% mem usage, is this normal?
Yes
INF: SQL Server Memory Usage
http://support.microsoft.com/defaul...b;en-us;q321363
> -If i assigned, for example, 40GB of memory would it just keep using
> memory until it had the hole db in memory (20gb db).
It might use slightly more RAM [than 20GB] because it would (could) have
data and query plans in cache. It might also decide that it wants
additional memory for SQL Agent, user connections, and so on.
> -If that's not the case when does it stop using memory?
When it does not need any more.
> Your thoughts,
> Thanks.
How to take back up using query analyzer
Hi
Can anybody tell me how to take database back up using query analyzer in sql
server 2000?
i dont want in enterprise manager i wnat to know how to do it with query
analyzer.
can you tell me y i'm getting this error when i'm trying to open enterprise
manager
"SQLDMO has not been registered, please re-run SQL SERVER setup and contact
your system administrator"
i can re-run setup but i need to take back up first and it is not giving any
error when opening sql query analyzer.
so can any one tell me
Thanx in advance
JyothiAnswered in microsoft.public.sqlserver.programming
Please do not multi-post.
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/
"yoshitha" <gudivada_kmm@.yahoo.co.in> wrote in message
news:%23uGZUP%23$FHA.1312@.TK2MSFTNGP09.phx.gbl...
> Hi
> Can anybody tell me how to take database back up using query analyzer in
> sql server 2000?
> i dont want in enterprise manager i wnat to know how to do it with query
> analyzer.
> can you tell me y i'm getting this error when i'm trying to open
> enterprise manager
> "SQLDMO has not been registered, please re-run SQL SERVER setup and
> contact your system administrator"
> i can re-run setup but i need to take back up first and it is not giving
> any error when opening sql query analyzer.
> so can any one tell me
> Thanx in advance
> Jyothi
>
Can anybody tell me how to take database back up using query analyzer in sql
server 2000?
i dont want in enterprise manager i wnat to know how to do it with query
analyzer.
can you tell me y i'm getting this error when i'm trying to open enterprise
manager
"SQLDMO has not been registered, please re-run SQL SERVER setup and contact
your system administrator"
i can re-run setup but i need to take back up first and it is not giving any
error when opening sql query analyzer.
so can any one tell me
Thanx in advance
JyothiAnswered in microsoft.public.sqlserver.programming
Please do not multi-post.
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/
"yoshitha" <gudivada_kmm@.yahoo.co.in> wrote in message
news:%23uGZUP%23$FHA.1312@.TK2MSFTNGP09.phx.gbl...
> Hi
> Can anybody tell me how to take database back up using query analyzer in
> sql server 2000?
> i dont want in enterprise manager i wnat to know how to do it with query
> analyzer.
> can you tell me y i'm getting this error when i'm trying to open
> enterprise manager
> "SQLDMO has not been registered, please re-run SQL SERVER setup and
> contact your system administrator"
> i can re-run setup but i need to take back up first and it is not giving
> any error when opening sql query analyzer.
> so can any one tell me
> Thanx in advance
> Jyothi
>
How to take back up using query analyzer
Hi
Can anybody tell me how to take database back up using query analyzer in sql
server 2000?
i dont want in enterprise manager i wnat to know how to do it with query
analyzer.
can you tell me y i'm getting this error when i'm trying to open enterprise
manager
"SQLDMO has not been registered, please re-run SQL SERVER setup and contact
your system administrator"
i can re-run setup but i need to take back up first and it is not giving any
error when opening sql query analyzer.
so can any one tell me
Thanx in advance
Jyothi
Answered in microsoft.public.sqlserver.programming
Please do not multi-post.
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/
"yoshitha" <gudivada_kmm@.yahoo.co.in> wrote in message
news:%23uGZUP%23$FHA.1312@.TK2MSFTNGP09.phx.gbl...
> Hi
> Can anybody tell me how to take database back up using query analyzer in
> sql server 2000?
> i dont want in enterprise manager i wnat to know how to do it with query
> analyzer.
> can you tell me y i'm getting this error when i'm trying to open
> enterprise manager
> "SQLDMO has not been registered, please re-run SQL SERVER setup and
> contact your system administrator"
> i can re-run setup but i need to take back up first and it is not giving
> any error when opening sql query analyzer.
> so can any one tell me
> Thanx in advance
> Jyothi
>
Can anybody tell me how to take database back up using query analyzer in sql
server 2000?
i dont want in enterprise manager i wnat to know how to do it with query
analyzer.
can you tell me y i'm getting this error when i'm trying to open enterprise
manager
"SQLDMO has not been registered, please re-run SQL SERVER setup and contact
your system administrator"
i can re-run setup but i need to take back up first and it is not giving any
error when opening sql query analyzer.
so can any one tell me
Thanx in advance
Jyothi
Answered in microsoft.public.sqlserver.programming
Please do not multi-post.
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/
"yoshitha" <gudivada_kmm@.yahoo.co.in> wrote in message
news:%23uGZUP%23$FHA.1312@.TK2MSFTNGP09.phx.gbl...
> Hi
> Can anybody tell me how to take database back up using query analyzer in
> sql server 2000?
> i dont want in enterprise manager i wnat to know how to do it with query
> analyzer.
> can you tell me y i'm getting this error when i'm trying to open
> enterprise manager
> "SQLDMO has not been registered, please re-run SQL SERVER setup and
> contact your system administrator"
> i can re-run setup but i need to take back up first and it is not giving
> any error when opening sql query analyzer.
> so can any one tell me
> Thanx in advance
> Jyothi
>
How to take back up using query analyzer
Hi
Can anybody tell me how to take database back up using query analyzer in sql
server 2000?
i dont want in enterprise manager i wnat to know how to do it with query
analyzer.
can you tell me y i'm getting this error when i'm trying to open enterprise
manager
"SQLDMO has not been registered, please re-run SQL SERVER setup and contact
your system administrator"
i can re-run setup but i need to take back up first and it is not giving any
error when opening sql query analyzer.
so can any one tell me
Thanx in advance
JyothiAnswered in microsoft.public.sqlserver.programming
Please do not multi-post.
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/
"yoshitha" <gudivada_kmm@.yahoo.co.in> wrote in message
news:%23uGZUP%23$FHA.1312@.TK2MSFTNGP09.phx.gbl...
> Hi
> Can anybody tell me how to take database back up using query analyzer in
> sql server 2000?
> i dont want in enterprise manager i wnat to know how to do it with query
> analyzer.
> can you tell me y i'm getting this error when i'm trying to open
> enterprise manager
> "SQLDMO has not been registered, please re-run SQL SERVER setup and
> contact your system administrator"
> i can re-run setup but i need to take back up first and it is not giving
> any error when opening sql query analyzer.
> so can any one tell me
> Thanx in advance
> Jyothi
>
Can anybody tell me how to take database back up using query analyzer in sql
server 2000?
i dont want in enterprise manager i wnat to know how to do it with query
analyzer.
can you tell me y i'm getting this error when i'm trying to open enterprise
manager
"SQLDMO has not been registered, please re-run SQL SERVER setup and contact
your system administrator"
i can re-run setup but i need to take back up first and it is not giving any
error when opening sql query analyzer.
so can any one tell me
Thanx in advance
JyothiAnswered in microsoft.public.sqlserver.programming
Please do not multi-post.
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/
"yoshitha" <gudivada_kmm@.yahoo.co.in> wrote in message
news:%23uGZUP%23$FHA.1312@.TK2MSFTNGP09.phx.gbl...
> Hi
> Can anybody tell me how to take database back up using query analyzer in
> sql server 2000?
> i dont want in enterprise manager i wnat to know how to do it with query
> analyzer.
> can you tell me y i'm getting this error when i'm trying to open
> enterprise manager
> "SQLDMO has not been registered, please re-run SQL SERVER setup and
> contact your system administrator"
> i can re-run setup but i need to take back up first and it is not giving
> any error when opening sql query analyzer.
> so can any one tell me
> Thanx in advance
> Jyothi
>
how to take back up
Hi
Can anybody tell me how to take database back up using query analyzer in sql
server 2000?
i dont want in enterprise manager i wnat to know how to do it with query
analyzer.
can you tell me y i'm getting this error when i'm trying to open enterprise
manager
"SQLDMO has not been registered, please re-run SQL SERVER setup and contact
your system administrator"
i can re-run setup but i need to take back up first and it is not giving any
error when opening sql query analyzer.
so can any one tell me
Thanx in advance
JyothiBACKUP DATABASE <dbname>
TO DISK = "d:\temp\backup.bak"
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/
"yoshitha" <gudivada_kmm@.yahoo.co.in> wrote in message
news:eA81FP%23$FHA.216@.TK2MSFTNGP15.phx.gbl...
> Hi
> Can anybody tell me how to take database back up using query analyzer in
> sql server 2000?
> i dont want in enterprise manager i wnat to know how to do it with query
> analyzer.
> can you tell me y i'm getting this error when i'm trying to open
> enterprise manager
> "SQLDMO has not been registered, please re-run SQL SERVER setup and
> contact your system administrator"
> i can re-run setup but i need to take back up first and it is not giving
> any error when opening sql query analyzer.
> so can any one tell me
> Thanx in advance
> Jyothi
>|||Hi
Check out the description of the backup command in Books online or at
http://msdn.microsoft.com/library/d...asp?frame=true
John
"yoshitha" wrote:
> Hi
> Can anybody tell me how to take database back up using query analyzer in s
ql
> server 2000?
> i dont want in enterprise manager i wnat to know how to do it with query
> analyzer.
> can you tell me y i'm getting this error when i'm trying to open enterpris
e
> manager
> "SQLDMO has not been registered, please re-run SQL SERVER setup and contac
t
> your system administrator"
> i can re-run setup but i need to take back up first and it is not giving a
ny
> error when opening sql query analyzer.
> so can any one tell me
> Thanx in advance
> Jyothi
>
>
Can anybody tell me how to take database back up using query analyzer in sql
server 2000?
i dont want in enterprise manager i wnat to know how to do it with query
analyzer.
can you tell me y i'm getting this error when i'm trying to open enterprise
manager
"SQLDMO has not been registered, please re-run SQL SERVER setup and contact
your system administrator"
i can re-run setup but i need to take back up first and it is not giving any
error when opening sql query analyzer.
so can any one tell me
Thanx in advance
JyothiBACKUP DATABASE <dbname>
TO DISK = "d:\temp\backup.bak"
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/
"yoshitha" <gudivada_kmm@.yahoo.co.in> wrote in message
news:eA81FP%23$FHA.216@.TK2MSFTNGP15.phx.gbl...
> Hi
> Can anybody tell me how to take database back up using query analyzer in
> sql server 2000?
> i dont want in enterprise manager i wnat to know how to do it with query
> analyzer.
> can you tell me y i'm getting this error when i'm trying to open
> enterprise manager
> "SQLDMO has not been registered, please re-run SQL SERVER setup and
> contact your system administrator"
> i can re-run setup but i need to take back up first and it is not giving
> any error when opening sql query analyzer.
> so can any one tell me
> Thanx in advance
> Jyothi
>|||Hi
Check out the description of the backup command in Books online or at
http://msdn.microsoft.com/library/d...asp?frame=true
John
"yoshitha" wrote:
> Hi
> Can anybody tell me how to take database back up using query analyzer in s
ql
> server 2000?
> i dont want in enterprise manager i wnat to know how to do it with query
> analyzer.
> can you tell me y i'm getting this error when i'm trying to open enterpris
e
> manager
> "SQLDMO has not been registered, please re-run SQL SERVER setup and contac
t
> your system administrator"
> i can re-run setup but i need to take back up first and it is not giving a
ny
> error when opening sql query analyzer.
> so can any one tell me
> Thanx in advance
> Jyothi
>
>
how to take a db into unrecovery mode and apply more log backups?
In SQL Server Enterprise Manager, I restored a db from its full, diff and two
log backups (there are 4 log backups for this db) and left the database
operational. But I did not find what I need in the restored db. So I wanted
to apply the rest two log backups to the db. What should I do to the
currently operational db so that I can apply more log backups on it?
Thanks,
BingBing,
From your comment, I assume that you have done something in the database and
may not be able to restore old logs any longer. I believe that you needed
to do your earlier restores with the STANDBY option. As below from the BOL:
STANDBY = undo_file_name
STANDBY allows a database to be brought up for read-only access between
transaction log restores and can be used with either warm standby server
situations or special recovery situations in which it is useful to inspect
the database between log restores.
RLF
"bing" <bing@.discussions.microsoft.com> wrote in message
news:76F7D171-AE5D-4A08-A489-87A0DB186724@.microsoft.com...
> In SQL Server Enterprise Manager, I restored a db from its full, diff and
two
> log backups (there are 4 log backups for this db) and left the database
> operational. But I did not find what I need in the restored db. So I
wanted
> to apply the rest two log backups to the db. What should I do to the
> currently operational db so that I can apply more log backups on it?
> Thanks,
> Bing|||Thanks, Russell. You read me right. And STANDBY is just what I need to do.
Bing
"Russell Fields" wrote:
> Bing,
> From your comment, I assume that you have done something in the database and
> may not be able to restore old logs any longer. I believe that you needed
> to do your earlier restores with the STANDBY option. As below from the BOL:
> STANDBY = undo_file_name
> STANDBY allows a database to be brought up for read-only access between
> transaction log restores and can be used with either warm standby server
> situations or special recovery situations in which it is useful to inspect
> the database between log restores.
> RLF
> "bing" <bing@.discussions.microsoft.com> wrote in message
> news:76F7D171-AE5D-4A08-A489-87A0DB186724@.microsoft.com...
> > In SQL Server Enterprise Manager, I restored a db from its full, diff and
> two
> > log backups (there are 4 log backups for this db) and left the database
> > operational. But I did not find what I need in the restored db. So I
> wanted
> > to apply the rest two log backups to the db. What should I do to the
> > currently operational db so that I can apply more log backups on it?
> >
> > Thanks,
> >
> > Bing
>
>
log backups (there are 4 log backups for this db) and left the database
operational. But I did not find what I need in the restored db. So I wanted
to apply the rest two log backups to the db. What should I do to the
currently operational db so that I can apply more log backups on it?
Thanks,
BingBing,
From your comment, I assume that you have done something in the database and
may not be able to restore old logs any longer. I believe that you needed
to do your earlier restores with the STANDBY option. As below from the BOL:
STANDBY = undo_file_name
STANDBY allows a database to be brought up for read-only access between
transaction log restores and can be used with either warm standby server
situations or special recovery situations in which it is useful to inspect
the database between log restores.
RLF
"bing" <bing@.discussions.microsoft.com> wrote in message
news:76F7D171-AE5D-4A08-A489-87A0DB186724@.microsoft.com...
> In SQL Server Enterprise Manager, I restored a db from its full, diff and
two
> log backups (there are 4 log backups for this db) and left the database
> operational. But I did not find what I need in the restored db. So I
wanted
> to apply the rest two log backups to the db. What should I do to the
> currently operational db so that I can apply more log backups on it?
> Thanks,
> Bing|||Thanks, Russell. You read me right. And STANDBY is just what I need to do.
Bing
"Russell Fields" wrote:
> Bing,
> From your comment, I assume that you have done something in the database and
> may not be able to restore old logs any longer. I believe that you needed
> to do your earlier restores with the STANDBY option. As below from the BOL:
> STANDBY = undo_file_name
> STANDBY allows a database to be brought up for read-only access between
> transaction log restores and can be used with either warm standby server
> situations or special recovery situations in which it is useful to inspect
> the database between log restores.
> RLF
> "bing" <bing@.discussions.microsoft.com> wrote in message
> news:76F7D171-AE5D-4A08-A489-87A0DB186724@.microsoft.com...
> > In SQL Server Enterprise Manager, I restored a db from its full, diff and
> two
> > log backups (there are 4 log backups for this db) and left the database
> > operational. But I did not find what I need in the restored db. So I
> wanted
> > to apply the rest two log backups to the db. What should I do to the
> > currently operational db so that I can apply more log backups on it?
> >
> > Thanks,
> >
> > Bing
>
>
how to take a db into unrecovery mode and apply more log backups?
In SQL Server Enterprise Manager, I restored a db from its full, diff and two
log backups (there are 4 log backups for this db) and left the database
operational. But I did not find what I need in the restored db. So I wanted
to apply the rest two log backups to the db. What should I do to the
currently operational db so that I can apply more log backups on it?
Thanks,
Bing
Bing,
From your comment, I assume that you have done something in the database and
may not be able to restore old logs any longer. I believe that you needed
to do your earlier restores with the STANDBY option. As below from the BOL:
STANDBY = undo_file_name
STANDBY allows a database to be brought up for read-only access between
transaction log restores and can be used with either warm standby server
situations or special recovery situations in which it is useful to inspect
the database between log restores.
RLF
"bing" <bing@.discussions.microsoft.com> wrote in message
news:76F7D171-AE5D-4A08-A489-87A0DB186724@.microsoft.com...
> In SQL Server Enterprise Manager, I restored a db from its full, diff and
two
> log backups (there are 4 log backups for this db) and left the database
> operational. But I did not find what I need in the restored db. So I
wanted
> to apply the rest two log backups to the db. What should I do to the
> currently operational db so that I can apply more log backups on it?
> Thanks,
> Bing
log backups (there are 4 log backups for this db) and left the database
operational. But I did not find what I need in the restored db. So I wanted
to apply the rest two log backups to the db. What should I do to the
currently operational db so that I can apply more log backups on it?
Thanks,
Bing
Bing,
From your comment, I assume that you have done something in the database and
may not be able to restore old logs any longer. I believe that you needed
to do your earlier restores with the STANDBY option. As below from the BOL:
STANDBY = undo_file_name
STANDBY allows a database to be brought up for read-only access between
transaction log restores and can be used with either warm standby server
situations or special recovery situations in which it is useful to inspect
the database between log restores.
RLF
"bing" <bing@.discussions.microsoft.com> wrote in message
news:76F7D171-AE5D-4A08-A489-87A0DB186724@.microsoft.com...
> In SQL Server Enterprise Manager, I restored a db from its full, diff and
two
> log backups (there are 4 log backups for this db) and left the database
> operational. But I did not find what I need in the restored db. So I
wanted
> to apply the rest two log backups to the db. What should I do to the
> currently operational db so that I can apply more log backups on it?
> Thanks,
> Bing
Monday, March 12, 2012
How to switch off automatic blanking of table views in enterprise manager ?
Hi Sqlserver experts,
EM locks data when it reads it. That is why MS releases the result set
after X amount of time. You should really use Query Analyzer to look at
data that you do not intend to change.
I don't think that's the case. I've just created a test table, filled
it with some data and viewed it in EM. I could still update one of the
viewed rows using QA. Once I re-ran the EM query using the exclamation
icon again, the changed row reflected its new state.
I agree! It's a much better tool for actually executing queries.|||Bobbo wrote:
>
I don't think that's the case. I've just created a test table, filled
it with some data and viewed it in EM. I could still update one of the
viewed rows using QA. Once I re-ran the EM query using the exclamation
icon again, the changed row reflected its new state.
>
Surely the result set clearing is because of the resources consumed by
the open connection, rather than any locking? If I'm wrong, somebody
stop me - to quote Jim Carey.
>
>
I agree! It's a much better tool for actually executing queries.
We have traced data access problems to users accessing data via EM. MS
may have modified some of the logic with SP1, SP2, SP3, and/or SP4 so
that EM works more effectively.
>From the SQL Server Documentation: Optimizing Query Performance -
SQL Server is essentially a puppet of the client application. The
client application has almost total control over (and responsibility
for) the locks acquired on the server. Although the SQL Server lock
manager automatically uses locks to protect transactions, this is
directly instigated by the query type sent from the client application
and the way the results are processed. Therefore, resolution of most
blocking problems involves inspecting the client application.
I use the SQL Server enterprise manager of MSSQL 2000 regularly.
I'm often annoyed by the automatic blanking of the table views.
If this happens then mostly with the hint :
"The Results pane have been cleared to conserve server resources.
To re-establish the result set, run query again."
Is there any possibility to switch that blanking off ?
Best regards,
Daniel WetzlerCan't be done. Microsoft has gone as far as to put out a Knowledge
Base article on this feature, with instructions to click 'No' when the
pop-up comes up. Not all that helpful, really.
They've fixed the problem in the new version, so it looks like you'll
remain out of luck.
Jason Kester
Expat Software Consulting Services
http://www.expatsoftware.com/
--
Get your own Travel Blog, with itinerary maps and photos!
http://www.blogabond.com/|||Thank you very much although its really bad news :-(((
Jason Kester schrieb:
Quote:
Originally Posted by
Can't be done. Microsoft has gone as far as to put out a Knowledge
Base article on this feature, with instructions to click 'No' when the
pop-up comes up. Not all that helpful, really.
>
They've fixed the problem in the new version, so it looks like you'll
remain out of luck.
>
Jason Kester
Expat Software Consulting Services
http://www.expatsoftware.com/
>
--
Get your own Travel Blog, with itinerary maps and photos!
http://www.blogabond.com/
Quote:
Originally Posted by
Thank you very much although its really bad news :-(((
>
>
Jason Kester schrieb:
>
Quote:
Originally Posted by
Can't be done. Microsoft has gone as far as to put out a Knowledge
Base article on this feature, with instructions to click 'No' when the
pop-up comes up. Not all that helpful, really.
They've fixed the problem in the new version, so it looks like you'll
remain out of luck.
Jason Kester
Expat Software Consulting Services
http://www.expatsoftware.com/
--
Get your own Travel Blog, with itinerary maps and photos!
http://www.blogabond.com/
EM locks data when it reads it. That is why MS releases the result set
after X amount of time. You should really use Query Analyzer to look at
data that you do not intend to change.
IMHO -- Mark D Powell --|||Mark D Powell wrote:
Quote:
Originally Posted by
EM locks data when it reads it.
I don't think that's the case. I've just created a test table, filled
it with some data and viewed it in EM. I could still update one of the
viewed rows using QA. Once I re-ran the EM query using the exclamation
icon again, the changed row reflected its new state.
Surely the result set clearing is because of the resources consumed by
the open connection, rather than any locking? If I'm wrong, somebody
stop me - to quote Jim Carey.
Quote:
Originally Posted by
You should really use Query Analyzer
I agree! It's a much better tool for actually executing queries.|||Bobbo wrote:
Quote:
Originally Posted by
Mark D Powell wrote:
>
Quote:
Originally Posted by
EM locks data when it reads it.
>
I don't think that's the case. I've just created a test table, filled
it with some data and viewed it in EM. I could still update one of the
viewed rows using QA. Once I re-ran the EM query using the exclamation
icon again, the changed row reflected its new state.
>
Surely the result set clearing is because of the resources consumed by
the open connection, rather than any locking? If I'm wrong, somebody
stop me - to quote Jim Carey.
>
Quote:
Originally Posted by
You should really use Query Analyzer
>
I agree! It's a much better tool for actually executing queries.
We have traced data access problems to users accessing data via EM. MS
may have modified some of the logic with SP1, SP2, SP3, and/or SP4 so
that EM works more effectively.
Quote:
Originally Posted by
Quote:
Originally Posted by
>>
>From the SQL Server Documentation: Optimizing Query Performance -
SQL Server is essentially a puppet of the client application. The
client application has almost total control over (and responsibility
for) the locks acquired on the server. Although the SQL Server lock
manager automatically uses locks to protect transactions, this is
directly instigated by the query type sent from the client application
and the way the results are processed. Therefore, resolution of most
blocking problems involves inspecting the client application.
A blocking problem frequently requires both the inspection of the exact
SQL statements submitted by the application and the exact behavior of
the application regarding connection management, processing of all
result rows, and so on. If the development tool does not allow explicit
control over connection management, query time-out, processing of
results, and so on, blocking problems may not be resolvable.
Possible cause of problems listed in the above article (these are
things to avoid)
Submitting queries with long execution times
Canceling queries that were not committed or rolled back. [The
application needs to issue a rollback or commit after a query is
cancelled in order to release held locks!]
Applications that are not processing all results to completion
Distributed client/server deadlocks
Locks are held for the length of time needed to protect the resource at
the level requested:
<<
So it depends on how the clients works if one user can cause more
contention than is reasonable. Cursor and especially select for update
cursors can result in unexpected locks waiting. Like I said we tested
and identified a problem, but it was a couple of SP ago.
-- Mark D Powell --
Sunday, February 19, 2012
How to stop automatic excution of a report?
Hi,
I have a report containing one multi-value parameter with default values given. When open I report in Report Manager, report executes automatically. I need to stop this automatic execution of report. I need to give user an option to check if default values are ok for him or not. Is there any way other than removing default value from parameter to do this?
Thanks in anticipation.
Saeed
Sorry, there is no way to achieve this behavior in Report Manager. You need to remove the default value, otherwise the report will render.|||It is unfortunate that this was not considered as a requirement during development. However, you can work around this by adding an additional report parameter. Add a Start Report parameter as a string with 1 non-queried availabIe value like 'Yes'. The report will not render until the user selects the only available option for that parameter. Its not the best solution but is a viable workaround to the default rendering problem.
|||HiRather than use default parameters in a report why dont you make the report show a list of valid values e.g. from a query and the user will sellect appropriate value.
e.g.
A report uses a paramater param1; create a dataset with a sql query that generates valid values and make your report parameter populate from this dataset. You can set the default value to null so that the report prompts for the parameters from the valid list.
How to stop automatic excution of a report?
Hi,
I have a report containing one multi-value parameter with default values given. When open I report in Report Manager, report executes automatically. I need to stop this automatic execution of report. I need to give user an option to check if default values are ok for him or not. Is there any way other than removing default value from parameter to do this?
Thanks in anticipation.
Saeed
Sorry, there is no way to achieve this behavior in Report Manager. You need to remove the default value, otherwise the report will render.|||It is unfortunate that this was not considered as a requirement during development. However, you can work around this by adding an additional report parameter. Add a Start Report parameter as a string with 1 non-queried availabIe value like 'Yes'. The report will not render until the user selects the only available option for that parameter. Its not the best solution but is a viable workaround to the default rendering problem.
|||HiRather than use default parameters in a report why dont you make the report show a list of valid values e.g. from a query and the user will sellect appropriate value.
e.g.
A report uses a paramater param1; create a dataset with a sql query that generates valid values and make your report parameter populate from this dataset. You can set the default value to null so that the report prompts for the parameters from the valid list.
Subscribe to:
Posts (Atom)