add memory?

Hi,
I'm checking my performance of sql 2000 ent. on a w2k adv. server. There
are 2gb's of memory available. the server is dedicated for sql server
(at least i think it is).
I've noticed that the counter sql server: cache manager - cache hit
ratio is on average 67-70. The counter sql server:buffer manager -
buffer cache hit ratio is always above 99%. SQL Server uses dynamic mem
alloc.
All other import counters like processor and physical disk shows low values.
Could there be a memory bottleneck where the asigned cache for sql is
too low?You donâ't have a memory issue.
From SQL Server Books Online (BOL):
â'SQL Server: Cache Manager Object
The Cache Manager object provides counters to monitor how Microsoft® SQL
Serverâ?¢ uses memory to store objects such as stored procedures, ad hoc and
prepared Transact-SQL statements, and triggers.â'
Any SP, Trigger or Transact-SQL statements which are being called for the
1st time will not have an Execution Plan kept in the Cache. Besides, there
are many scenarios when SQL Server decides to generate a fresh Execution
Plan.
Have a look at the â'Execution Plan Caching and Reuseâ' topic in the BOL.
"Jason" wrote:
> Hi,
> I'm checking my performance of sql 2000 ent. on a w2k adv. server. There
> are 2gb's of memory available. the server is dedicated for sql server
> (at least i think it is).
> I've noticed that the counter sql server: cache manager - cache hit
> ratio is on average 67-70. The counter sql server:buffer manager -
> buffer cache hit ratio is always above 99%. SQL Server uses dynamic mem
> alloc.
> All other import counters like processor and physical disk shows low values.
> Could there be a memory bottleneck where the asigned cache for sql is
> too low?
>

add memory?

Hi,
I'm checking my performance of sql 2000 ent. on a w2k adv. server. There
are 2gb's of memory available. the server is dedicated for sql server
(at least i think it is).
I've noticed that the counter sql server: cache manager - cache hit
ratio is on average 67-70. The counter sql server:buffer manager -
buffer cache hit ratio is always above 99%. SQL Server uses dynamic mem
alloc.
All other import counters like processor and physical disk shows low values.
Could there be a memory bottleneck where the asigned cache for sql is
too low?You don’t have a memory issue.
From SQL Server Books Online (BOL):
“SQL Server: Cache Manager Object
The Cache Manager object provides counters to monitor how Microsoft? SQL
Server? uses memory to store objects such as stored procedures, ad hoc and
prepared Transact-SQL statements, and triggers.”
Any SP, Trigger or Transact-SQL statements which are being called for the
1st time will not have an Execution Plan kept in the Cache. Besides, there
are many scenarios when SQL Server decides to generate a fresh Execution
Plan.
Have a look at the ‘Execution Plan Caching and Reuse’ topic in the BOL.
"Jason" wrote:

> Hi,
> I'm checking my performance of sql 2000 ent. on a w2k adv. server. There
> are 2gb's of memory available. the server is dedicated for sql server
> (at least i think it is).
> I've noticed that the counter sql server: cache manager - cache hit
> ratio is on average 67-70. The counter sql server:buffer manager -
> buffer cache hit ratio is always above 99%. SQL Server uses dynamic mem
> alloc.
> All other import counters like processor and physical disk shows low value
s.
> Could there be a memory bottleneck where the asigned cache for sql is
> too low?
>

Adapters in SSIS?

Are there adapters available to connect to SSIS for

1. Siebel

2. IBM MQ

Please let me know what are the alternatives if they don't exist.

I am still struggling to understand the core functionality difference between BizTalk and SSIS?

Thank you.

Not out of the box but I believe a company called Attunity build adapters for other systems so you might find them useful.

Core difference between SSIS and BizTalk? That's an incredibly open question. At a very very high level BizTalk is for interactive real-time integration typically on small data packets whereas SSIS is batch and works on much larger volumes of data.

You wouldn't want to move 1m rows about with BizTalk and similarly you wouldn't want to integrate your eCommerce app with your supply-chain app using SSIS.

Hope that helps.

-Jamie

|||Hi Jamie, thank you for your response. So does that mean, integrating applications goes with BizTalk and moving bulk data goes with SSIS? Please explain a little bit further if you can. I am trying to really understand how and why SSIS is different from BizTalk
|||

Yeah, that is another way of stating what I said.

By sheer coincidence I've just come across this useful post explaining the difference between SSIS and BizTalk http://blogs.msdn.com/william_zentmayer/archive/2005/10/17/481992.aspx

Perhaps googling would help: http://www.google.co.uk/search?hl=en&q=biztalk+ssis&meta=

-Jamie

Ad hoc Reporting

Is adhoc reporting available in SRS 2000?

Thanks

No. Report Builder was shipped in SQL 2005|||If you are willing to invest some $$'s, check out Cizer's ad-hoc query builder (it's web based, which is kind of nice, and they have a version for 2000): www.cizer.com

Ad hoc Reporting

Is adhoc reporting available in SRS 2000?

Thanks

No. Report Builder was shipped in SQL 2005|||If you are willing to invest some $$'s, check out Cizer's ad-hoc query builder (it's web based, which is kind of nice, and they have a version for 2000): www.cizer.com

Actual size of database

My database size is of 1500 mb and actual data is not of 1500 mb the data
space available is showing 100 mb , i have done dbcc checkbd on the database
but still the it isnot showing actual size there is one more commond to
resize the database can anbody tell me
Yousuf Khan
Programmer
Yousuf wrote:
> My database size is of 1500 mb and actual data is not of 1500 mb the
> data space available is showing 100 mb , i have done dbcc checkbd on
> the database but still the it isnot showing actual size there is one
> more commond to resize the database can anbody tell me
If you need to shrink the data of log files because they have grown much
too large for what your database requires, you can use DBCC SHRINKFILE.
Having extra space in the data and log files is a good idea as auto-grow
operations are very expesinsive.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||Hi,
Use the below command to get the actual free space:-
For Data and Index
use dbname
go
sp_spaceused @.updateusage='true'
For Transaction log
DBCC SQLPERF(LOGSPACE)
Based on the outcome you can shrink the MDF and LDF file seperately.
Steps:-
1. Backup the transaction log (Backup Log in books online)
2. Now shrink the files
dbcc shrinkfile('logical_mdf_name',Xsize)
3. Shrink the LDF file
dbcc shrinkfile('logical_ldf_name',Xsize)
4. After this check the size again
use dbname
go
sp_spaceused @.updateusage='true'
For Transaction log
DBCC SQLPERF(LOGSPACE)
Thanks
Hari
SQL Server MVP
"Yousuf" <yousuf.yk@.gmail.com> wrote in message
news:B062771E-F552-4EBE-8F6E-2E2F0BD359EA@.microsoft.com...
> My database size is of 1500 mb and actual data is not of 1500 mb the data
> space available is showing 100 mb , i have done dbcc checkbd on the
> database
> but still the it isnot showing actual size there is one more commond to
> resize the database can anbody tell me
> --
> Yousuf Khan
> Programmer
|||thanks hari
being in the current database
if use DBCC UPDATEUSAGE will it be ok
or shall i go as per your advise
Yousuf Khan
Programmer
"Hari Prasad" wrote:

> Hi,
> Use the below command to get the actual free space:-
> For Data and Index
> use dbname
> go
> sp_spaceused @.updateusage='true'
> For Transaction log
> DBCC SQLPERF(LOGSPACE)
> Based on the outcome you can shrink the MDF and LDF file seperately.
>
> Steps:-
> 1. Backup the transaction log (Backup Log in books online)
> 2. Now shrink the files
> dbcc shrinkfile('logical_mdf_name',Xsize)
> 3. Shrink the LDF file
> dbcc shrinkfile('logical_ldf_name',Xsize)
> 4. After this check the size again
> use dbname
> go
> sp_spaceused @.updateusage='true'
>
> For Transaction log
> DBCC SQLPERF(LOGSPACE)
> --
> Thanks
> Hari
> SQL Server MVP
> "Yousuf" <yousuf.yk@.gmail.com> wrote in message
> news:B062771E-F552-4EBE-8F6E-2E2F0BD359EA@.microsoft.com...
>
>

Actual size of database

My database size is of 1500 mb and actual data is not of 1500 mb the data
space available is showing 100 mb , i have done dbcc checkbd on the database
but still the it isnot showing actual size there is one more commond to
resize the database can anbody tell me
--
Yousuf Khan
ProgrammerYousuf wrote:
> My database size is of 1500 mb and actual data is not of 1500 mb the
> data space available is showing 100 mb , i have done dbcc checkbd on
> the database but still the it isnot showing actual size there is one
> more commond to resize the database can anbody tell me
If you need to shrink the data of log files because they have grown much
too large for what your database requires, you can use DBCC SHRINKFILE.
Having extra space in the data and log files is a good idea as auto-grow
operations are very expesinsive.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Hi,
Use the below command to get the actual free space:-
For Data and Index
use dbname
go
sp_spaceused @.updateusage='true'
For Transaction log
DBCC SQLPERF(LOGSPACE)
Based on the outcome you can shrink the MDF and LDF file seperately.
Steps:-
1. Backup the transaction log (Backup Log in books online)
2. Now shrink the files
dbcc shrinkfile('logical_mdf_name',­size)
3. Shrink the LDF file
dbcc shrinkfile('logical_ldf_name',­size)
4. After this check the size again
use dbname
go
sp_spaceused @.updateusage='true'
For Transaction log
DBCC SQLPERF(LOGSPACE)
--
Thanks
Hari
SQL Server MVP
"Yousuf" <yousuf.yk@.gmail.com> wrote in message
news:B062771E-F552-4EBE-8F6E-2E2F0BD359EA@.microsoft.com...
> My database size is of 1500 mb and actual data is not of 1500 mb the data
> space available is showing 100 mb , i have done dbcc checkbd on the
> database
> but still the it isnot showing actual size there is one more commond to
> resize the database can anbody tell me
> --
> Yousuf Khan
> Programmer|||thanks hari
being in the current database
if use DBCC UPDATEUSAGE will it be ok
or shall i go as per your advise
Yousuf Khan
Programmer
"Hari Prasad" wrote:
> Hi,
> Use the below command to get the actual free space:-
> For Data and Index
> use dbname
> go
> sp_spaceused @.updateusage='true'
> For Transaction log
> DBCC SQLPERF(LOGSPACE)
> Based on the outcome you can shrink the MDF and LDF file seperately.
>
> Steps:-
> 1. Backup the transaction log (Backup Log in books online)
> 2. Now shrink the files
> dbcc shrinkfile('logical_mdf_name',­size)
> 3. Shrink the LDF file
> dbcc shrinkfile('logical_ldf_name',­size)
> 4. After this check the size again
> use dbname
> go
> sp_spaceused @.updateusage='true'
>
> For Transaction log
> DBCC SQLPERF(LOGSPACE)
> --
> Thanks
> Hari
> SQL Server MVP
> "Yousuf" <yousuf.yk@.gmail.com> wrote in message
> news:B062771E-F552-4EBE-8F6E-2E2F0BD359EA@.microsoft.com...
> > My database size is of 1500 mb and actual data is not of 1500 mb the data
> > space available is showing 100 mb , i have done dbcc checkbd on the
> > database
> > but still the it isnot showing actual size there is one more commond to
> > resize the database can anbody tell me
> > --
> > Yousuf Khan
> > Programmer
>
>

Actual size of database

My database size is of 1500 mb and actual data is not of 1500 mb the data
space available is showing 100 mb , i have done dbcc checkbd on the database
but still the it isnot showing actual size there is one more commond to
resize the database can anbody tell me
--
Yousuf Khan
ProgrammerYousuf wrote:
> My database size is of 1500 mb and actual data is not of 1500 mb the
> data space available is showing 100 mb , i have done dbcc checkbd on
> the database but still the it isnot showing actual size there is one
> more commond to resize the database can anbody tell me
If you need to shrink the data of log files because they have grown much
too large for what your database requires, you can use DBCC SHRINKFILE.
Having extra space in the data and log files is a good idea as auto-grow
operations are very expesinsive.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Hi,
Use the below command to get the actual free space:-
For Data and Index
use dbname
go
sp_spaceused @.updateusage='true'
For Transaction log
DBCC SQLPERF(LOGSPACE)
Based on the outcome you can shrink the MDF and LDF file seperately.
Steps:-
1. Backup the transaction log (Backup Log in books online)
2. Now shrink the files
dbcc shrinkfile('logical_mdf_name',_size)
3. Shrink the LDF file
dbcc shrinkfile('logical_ldf_name',_size)
4. After this check the size again
use dbname
go
sp_spaceused @.updateusage='true'
For Transaction log
DBCC SQLPERF(LOGSPACE)
Thanks
Hari
SQL Server MVP
"Yousuf" <yousuf.yk@.gmail.com> wrote in message
news:B062771E-F552-4EBE-8F6E-2E2F0BD359EA@.microsoft.com...
> My database size is of 1500 mb and actual data is not of 1500 mb the data
> space available is showing 100 mb , i have done dbcc checkbd on the
> database
> but still the it isnot showing actual size there is one more commond to
> resize the database can anbody tell me
> --
> Yousuf Khan
> Programmer|||thanks hari
being in the current database
if use DBCC UPDATEUSAGE will it be ok
or shall i go as per your advise
Yousuf Khan
Programmer
"Hari Prasad" wrote:

> Hi,
> Use the below command to get the actual free space:-
> For Data and Index
> use dbname
> go
> sp_spaceused @.updateusage='true'
> For Transaction log
> DBCC SQLPERF(LOGSPACE)
> Based on the outcome you can shrink the MDF and LDF file seperately.
>
> Steps:-
> 1. Backup the transaction log (Backup Log in books online)
> 2. Now shrink the files
> dbcc shrinkfile('logical_mdf_name',_size)
> 3. Shrink the LDF file
> dbcc shrinkfile('logical_ldf_name',_size)
> 4. After this check the size again
> use dbname
> go
> sp_spaceused @.updateusage='true'
>
> For Transaction log
> DBCC SQLPERF(LOGSPACE)
> --
> Thanks
> Hari
> SQL Server MVP
> "Yousuf" <yousuf.yk@.gmail.com> wrote in message
> news:B062771E-F552-4EBE-8F6E-2E2F0BD359EA@.microsoft.com...
>
>