I added several indexes and statistics to a SQL 2000
database, and the next day I found that 4 of the
statistics no longer exist. Is there any way that the
auto create/update statistics could have caused this? Or
anything else, other than dropping them?
In addition, what effect would this have on my query
performance? I'm a little unsure about how the indexes
and statistics work together, but any help would be
greatly appreciated.
Thank you,
HeidiI guess somebody or some job deleted that statistics. SQL dose not delete
index or statistics by itself.
Since, SQL server dose cost based optimization, the statistics is very
important to decide the good plan. it must be up to date.
"hdsjunk" <anonymous@.discussions.microsoft.com> wrote in message
news:103d01c48bc9$682e5210$a301280a@.phx.gbl...
> I added several indexes and statistics to a SQL 2000
> database, and the next day I found that 4 of the
> statistics no longer exist. Is there any way that the
> auto create/update statistics could have caused this? Or
> anything else, other than dropping them?
> In addition, what effect would this have on my query
> performance? I'm a little unsure about how the indexes
> and statistics work together, but any help would be
> greatly appreciated.
> Thank you,
> Heidi|||Heidi,
It is likely that a job or other process, or even a person deleted these
statistics. SQL Server won't delete statistics without being asked.
If you do not have statistics on larger tables, SQL Server finds it
difficult to know what indexes to choose when compiling the query plan.
It will quite often choose the wrong index if you do not have
statistics, or if your statistics are wildly inaccurate (out-of-date).
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
hdsjunk wrote:
> I added several indexes and statistics to a SQL 2000
> database, and the next day I found that 4 of the
> statistics no longer exist. Is there any way that the
> auto create/update statistics could have caused this? Or
> anything else, other than dropping them?
> In addition, what effect would this have on my query
> performance? I'm a little unsure about how the indexes
> and statistics work together, but any help would be
> greatly appreciated.
> Thank you,
> Heidi
Showing posts with label statistics. Show all posts
Showing posts with label statistics. Show all posts
Tuesday, March 27, 2012
Change in Statistics
I added several indexes and statistics to a SQL 2000
database, and the next day I found that 4 of the
statistics no longer exist. Is there any way that the
auto create/update statistics could have caused this? Or
anything else, other than dropping them?
In addition, what effect would this have on my query
performance? I'm a little unsure about how the indexes
and statistics work together, but any help would be
greatly appreciated.
Thank you,
Heidi
I guess somebody or some job deleted that statistics. SQL dose not delete
index or statistics by itself.
Since, SQL server dose cost based optimization, the statistics is very
important to decide the good plan. it must be up to date.
"hdsjunk" <anonymous@.discussions.microsoft.com> wrote in message
news:103d01c48bc9$682e5210$a301280a@.phx.gbl...
> I added several indexes and statistics to a SQL 2000
> database, and the next day I found that 4 of the
> statistics no longer exist. Is there any way that the
> auto create/update statistics could have caused this? Or
> anything else, other than dropping them?
> In addition, what effect would this have on my query
> performance? I'm a little unsure about how the indexes
> and statistics work together, but any help would be
> greatly appreciated.
> Thank you,
> Heidi
|||Heidi,
It is likely that a job or other process, or even a person deleted these
statistics. SQL Server won't delete statistics without being asked.
If you do not have statistics on larger tables, SQL Server finds it
difficult to know what indexes to choose when compiling the query plan.
It will quite often choose the wrong index if you do not have
statistics, or if your statistics are wildly inaccurate (out-of-date).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
hdsjunk wrote:
> I added several indexes and statistics to a SQL 2000
> database, and the next day I found that 4 of the
> statistics no longer exist. Is there any way that the
> auto create/update statistics could have caused this? Or
> anything else, other than dropping them?
> In addition, what effect would this have on my query
> performance? I'm a little unsure about how the indexes
> and statistics work together, but any help would be
> greatly appreciated.
> Thank you,
> Heidi
sql
database, and the next day I found that 4 of the
statistics no longer exist. Is there any way that the
auto create/update statistics could have caused this? Or
anything else, other than dropping them?
In addition, what effect would this have on my query
performance? I'm a little unsure about how the indexes
and statistics work together, but any help would be
greatly appreciated.
Thank you,
Heidi
I guess somebody or some job deleted that statistics. SQL dose not delete
index or statistics by itself.
Since, SQL server dose cost based optimization, the statistics is very
important to decide the good plan. it must be up to date.
"hdsjunk" <anonymous@.discussions.microsoft.com> wrote in message
news:103d01c48bc9$682e5210$a301280a@.phx.gbl...
> I added several indexes and statistics to a SQL 2000
> database, and the next day I found that 4 of the
> statistics no longer exist. Is there any way that the
> auto create/update statistics could have caused this? Or
> anything else, other than dropping them?
> In addition, what effect would this have on my query
> performance? I'm a little unsure about how the indexes
> and statistics work together, but any help would be
> greatly appreciated.
> Thank you,
> Heidi
|||Heidi,
It is likely that a job or other process, or even a person deleted these
statistics. SQL Server won't delete statistics without being asked.
If you do not have statistics on larger tables, SQL Server finds it
difficult to know what indexes to choose when compiling the query plan.
It will quite often choose the wrong index if you do not have
statistics, or if your statistics are wildly inaccurate (out-of-date).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
hdsjunk wrote:
> I added several indexes and statistics to a SQL 2000
> database, and the next day I found that 4 of the
> statistics no longer exist. Is there any way that the
> auto create/update statistics could have caused this? Or
> anything else, other than dropping them?
> In addition, what effect would this have on my query
> performance? I'm a little unsure about how the indexes
> and statistics work together, but any help would be
> greatly appreciated.
> Thank you,
> Heidi
sql
Change in Statistics
I added several indexes and statistics to a SQL 2000
database, and the next day I found that 4 of the
statistics no longer exist. Is there any way that the
auto create/update statistics could have caused this? Or
anything else, other than dropping them?
In addition, what effect would this have on my query
performance? I'm a little unsure about how the indexes
and statistics work together, but any help would be
greatly appreciated.
Thank you,
HeidiI guess somebody or some job deleted that statistics. SQL dose not delete
index or statistics by itself.
Since, SQL server dose cost based optimization, the statistics is very
important to decide the good plan. it must be up to date.
"hdsjunk" <anonymous@.discussions.microsoft.com> wrote in message
news:103d01c48bc9$682e5210$a301280a@.phx.gbl...
> I added several indexes and statistics to a SQL 2000
> database, and the next day I found that 4 of the
> statistics no longer exist. Is there any way that the
> auto create/update statistics could have caused this? Or
> anything else, other than dropping them?
> In addition, what effect would this have on my query
> performance? I'm a little unsure about how the indexes
> and statistics work together, but any help would be
> greatly appreciated.
> Thank you,
> Heidi|||Heidi,
It is likely that a job or other process, or even a person deleted these
statistics. SQL Server won't delete statistics without being asked.
If you do not have statistics on larger tables, SQL Server finds it
difficult to know what indexes to choose when compiling the query plan.
It will quite often choose the wrong index if you do not have
statistics, or if your statistics are wildly inaccurate (out-of-date).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
hdsjunk wrote:
> I added several indexes and statistics to a SQL 2000
> database, and the next day I found that 4 of the
> statistics no longer exist. Is there any way that the
> auto create/update statistics could have caused this? Or
> anything else, other than dropping them?
> In addition, what effect would this have on my query
> performance? I'm a little unsure about how the indexes
> and statistics work together, but any help would be
> greatly appreciated.
> Thank you,
> Heidi
database, and the next day I found that 4 of the
statistics no longer exist. Is there any way that the
auto create/update statistics could have caused this? Or
anything else, other than dropping them?
In addition, what effect would this have on my query
performance? I'm a little unsure about how the indexes
and statistics work together, but any help would be
greatly appreciated.
Thank you,
HeidiI guess somebody or some job deleted that statistics. SQL dose not delete
index or statistics by itself.
Since, SQL server dose cost based optimization, the statistics is very
important to decide the good plan. it must be up to date.
"hdsjunk" <anonymous@.discussions.microsoft.com> wrote in message
news:103d01c48bc9$682e5210$a301280a@.phx.gbl...
> I added several indexes and statistics to a SQL 2000
> database, and the next day I found that 4 of the
> statistics no longer exist. Is there any way that the
> auto create/update statistics could have caused this? Or
> anything else, other than dropping them?
> In addition, what effect would this have on my query
> performance? I'm a little unsure about how the indexes
> and statistics work together, but any help would be
> greatly appreciated.
> Thank you,
> Heidi|||Heidi,
It is likely that a job or other process, or even a person deleted these
statistics. SQL Server won't delete statistics without being asked.
If you do not have statistics on larger tables, SQL Server finds it
difficult to know what indexes to choose when compiling the query plan.
It will quite often choose the wrong index if you do not have
statistics, or if your statistics are wildly inaccurate (out-of-date).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
hdsjunk wrote:
> I added several indexes and statistics to a SQL 2000
> database, and the next day I found that 4 of the
> statistics no longer exist. Is there any way that the
> auto create/update statistics could have caused this? Or
> anything else, other than dropping them?
> In addition, what effect would this have on my query
> performance? I'm a little unsure about how the indexes
> and statistics work together, but any help would be
> greatly appreciated.
> Thank you,
> Heidi
Friday, February 24, 2012
Centralized reports logging
We are using sql server 2000 reporting services. Management needs to know the
list of reports actually used, their frequency, and all the statistics along
with each one of them such as who, when, where, how long etc.
One way to that is to create a table in sql server and log all the facts
related to these attributes when the report(s) are launched at the front end
(asp.net) side. I am thinking out loud that SSRS must be logging this
information some where.
Is there any way to get to it? If yes, then how. I will google and look at
BOL to see if this could be done. In the mean time, any hints, pointers are
greatly appreciated.
Thank you in advance...RS has a series of reports that include packages you schedule (from SQL
Server). I haven't done this yet (I am doing it for RS 2005 but it uses
Integration Services instead of DTS).
RS 2000 steps
1.Reports you can download
2. Create table
3. Create DTS and schedule. This loads the table with info on usage
4. Run or schedule to run the management reports
You definitely do not need to roll you own with this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"sqlster" <nospam@.nospam.com> wrote in message
news:9A9FF399-FF68-45D7-B60D-C1A1BF21242F@.microsoft.com...
> We are using sql server 2000 reporting services. Management needs to know
> the
> list of reports actually used, their frequency, and all the statistics
> along
> with each one of them such as who, when, where, how long etc.
> One way to that is to create a table in sql server and log all the facts
> related to these attributes when the report(s) are launched at the front
> end
> (asp.net) side. I am thinking out loud that SSRS must be logging this
> information some where.
> Is there any way to get to it? If yes, then how. I will google and look at
> BOL to see if this could be done. In the mean time, any hints, pointers
> are
> greatly appreciated.
> Thank you in advance...
list of reports actually used, their frequency, and all the statistics along
with each one of them such as who, when, where, how long etc.
One way to that is to create a table in sql server and log all the facts
related to these attributes when the report(s) are launched at the front end
(asp.net) side. I am thinking out loud that SSRS must be logging this
information some where.
Is there any way to get to it? If yes, then how. I will google and look at
BOL to see if this could be done. In the mean time, any hints, pointers are
greatly appreciated.
Thank you in advance...RS has a series of reports that include packages you schedule (from SQL
Server). I haven't done this yet (I am doing it for RS 2005 but it uses
Integration Services instead of DTS).
RS 2000 steps
1.Reports you can download
2. Create table
3. Create DTS and schedule. This loads the table with info on usage
4. Run or schedule to run the management reports
You definitely do not need to roll you own with this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"sqlster" <nospam@.nospam.com> wrote in message
news:9A9FF399-FF68-45D7-B60D-C1A1BF21242F@.microsoft.com...
> We are using sql server 2000 reporting services. Management needs to know
> the
> list of reports actually used, their frequency, and all the statistics
> along
> with each one of them such as who, when, where, how long etc.
> One way to that is to create a table in sql server and log all the facts
> related to these attributes when the report(s) are launched at the front
> end
> (asp.net) side. I am thinking out loud that SSRS must be logging this
> information some where.
> Is there any way to get to it? If yes, then how. I will google and look at
> BOL to see if this could be done. In the mean time, any hints, pointers
> are
> greatly appreciated.
> Thank you in advance...
Subscribe to:
Posts (Atom)