database import question

Hi all,
I have a database I maintain that has grown quite large. The part of it
I am interested in, is one paticular table that logs the history of
certain high volume "events". I have events back to 2002, and the
database is almost 3 Gigs. I rarely need to query more than 6 months
worth. Here is what I would like to do.
I'd like to split the database, and create an archive database. I want
to move everything before 2006 to this new database. Now, I know I can
do a complete backup, and then delete the stuff I don't need, but I
wanted to know if there is a way to import just the dates I need from
the current database. Of course, there is a timedate field to key off
of.
I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
2003 Server.
Thanks in advance.Hi there
There are several ways to do this. You can try to use DTS to move the data
over. Or you can use query analyzer. If you can use Query Analyzer, you can
actually use a query something like:
SELECT *
INTO [ArchiveDBName].dbo.[TableName]
FROM dbo.[OriginalDBName]
WHERE [DateStamp] < '1/1/2006'
And to delete the records from the original table:
DELETE FROM dbo.[OriginalDBName]
WHERE [DateStamp] < '1/1/2006'
However, it was not clear from you post if you have access to Query Analyzer
.
Lucas
"mattdaddym@.gmail.com" wrote:

> Hi all,
> I have a database I maintain that has grown quite large. The part of it
> I am interested in, is one paticular table that logs the history of
> certain high volume "events". I have events back to 2002, and the
> database is almost 3 Gigs. I rarely need to query more than 6 months
> worth. Here is what I would like to do.
> I'd like to split the database, and create an archive database. I want
> to move everything before 2006 to this new database. Now, I know I can
> do a complete backup, and then delete the stuff I don't need, but I
> wanted to know if there is a way to import just the dates I need from
> the current database. Of course, there is a timedate field to key off
> of.
> I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
> 2003 Server.
> Thanks in advance.
>|||I do have access to query analyzer. I was hoping for a way to do it in
the GUI since it creats the tables automatically when you do an import.
I don't know for sure, but I will assume if I use your command that I
will need to set the table up first. Not a big deal, though. I guess
I'm just being lazy. Thank you!
Lucas Kartawidjaja wrote:[vbcol=seagreen]
> Hi there
> There are several ways to do this. You can try to use DTS to move the data
> over. Or you can use query analyzer. If you can use Query Analyzer, you ca
n
> actually use a query something like:
> SELECT *
> INTO [ArchiveDBName].dbo.[TableName]
> FROM dbo.[OriginalDBName]
> WHERE [DateStamp] < '1/1/2006'
> And to delete the records from the original table:
> DELETE FROM dbo.[OriginalDBName]
> WHERE [DateStamp] < '1/1/2006'
> However, it was not clear from you post if you have access to Query Analyz
er.
> Lucas
>
> "mattdaddym@.gmail.com" wrote:
>|||Actually with the SELECT INTO statement the beauty of it is that you don't
need to create the table first. SELECT INTO will create it for you the table
structure will be the same as the original table.
Lucas
"mattdaddym@.gmail.com" wrote:

> I do have access to query analyzer. I was hoping for a way to do it in
> the GUI since it creats the tables automatically when you do an import.
> I don't know for sure, but I will assume if I use your command that I
> will need to set the table up first. Not a big deal, though. I guess
> I'm just being lazy. Thank you!
> Lucas Kartawidjaja wrote:
>|||That is great. Thank you!
Lucas Kartawidjaja wrote:[vbcol=seagreen]
> Actually with the SELECT INTO statement the beauty of it is that you don't
> need to create the table first. SELECT INTO will create it for you the tab
le
> structure will be the same as the original table.
> Lucas
> "mattdaddym@.gmail.com" wrote:
>

database import question

Hi all,
I have a database I maintain that has grown quite large. The part of it
I am interested in, is one paticular table that logs the history of
certain high volume "events". I have events back to 2002, and the
database is almost 3 Gigs. I rarely need to query more than 6 months
worth. Here is what I would like to do.
I'd like to split the database, and create an archive database. I want
to move everything before 2006 to this new database. Now, I know I can
do a complete backup, and then delete the stuff I don't need, but I
wanted to know if there is a way to import just the dates I need from
the current database. Of course, there is a timedate field to key off
of.
I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
2003 Server.
Thanks in advance.Hi there
There are several ways to do this. You can try to use DTS to move the data
over. Or you can use query analyzer. If you can use Query Analyzer, you can
actually use a query something like:
SELECT *
INTO [ArchiveDBName].dbo.[TableName]
FROM dbo.[OriginalDBName]
WHERE [DateStamp] < '1/1/2006'
And to delete the records from the original table:
DELETE FROM dbo.[OriginalDBName]
WHERE [DateStamp] < '1/1/2006'
However, it was not clear from you post if you have access to Query Analyzer.
Lucas
"mattdaddym@.gmail.com" wrote:
> Hi all,
> I have a database I maintain that has grown quite large. The part of it
> I am interested in, is one paticular table that logs the history of
> certain high volume "events". I have events back to 2002, and the
> database is almost 3 Gigs. I rarely need to query more than 6 months
> worth. Here is what I would like to do.
> I'd like to split the database, and create an archive database. I want
> to move everything before 2006 to this new database. Now, I know I can
> do a complete backup, and then delete the stuff I don't need, but I
> wanted to know if there is a way to import just the dates I need from
> the current database. Of course, there is a timedate field to key off
> of.
> I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
> 2003 Server.
> Thanks in advance.
>|||I do have access to query analyzer. I was hoping for a way to do it in
the GUI since it creats the tables automatically when you do an import.
I don't know for sure, but I will assume if I use your command that I
will need to set the table up first. Not a big deal, though. I guess
I'm just being lazy. Thank you!
Lucas Kartawidjaja wrote:
> Hi there
> There are several ways to do this. You can try to use DTS to move the data
> over. Or you can use query analyzer. If you can use Query Analyzer, you can
> actually use a query something like:
> SELECT *
> INTO [ArchiveDBName].dbo.[TableName]
> FROM dbo.[OriginalDBName]
> WHERE [DateStamp] < '1/1/2006'
> And to delete the records from the original table:
> DELETE FROM dbo.[OriginalDBName]
> WHERE [DateStamp] < '1/1/2006'
> However, it was not clear from you post if you have access to Query Analyzer.
> Lucas
>
> "mattdaddym@.gmail.com" wrote:
> > Hi all,
> >
> > I have a database I maintain that has grown quite large. The part of it
> > I am interested in, is one paticular table that logs the history of
> > certain high volume "events". I have events back to 2002, and the
> > database is almost 3 Gigs. I rarely need to query more than 6 months
> > worth. Here is what I would like to do.
> >
> > I'd like to split the database, and create an archive database. I want
> > to move everything before 2006 to this new database. Now, I know I can
> > do a complete backup, and then delete the stuff I don't need, but I
> > wanted to know if there is a way to import just the dates I need from
> > the current database. Of course, there is a timedate field to key off
> > of.
> >
> > I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
> > 2003 Server.
> >
> > Thanks in advance.
> >
> >|||Actually with the SELECT INTO statement the beauty of it is that you don't
need to create the table first. SELECT INTO will create it for you the table
structure will be the same as the original table.
Lucas
"mattdaddym@.gmail.com" wrote:
> I do have access to query analyzer. I was hoping for a way to do it in
> the GUI since it creats the tables automatically when you do an import.
> I don't know for sure, but I will assume if I use your command that I
> will need to set the table up first. Not a big deal, though. I guess
> I'm just being lazy. Thank you!
> Lucas Kartawidjaja wrote:
> > Hi there
> >
> > There are several ways to do this. You can try to use DTS to move the data
> > over. Or you can use query analyzer. If you can use Query Analyzer, you can
> > actually use a query something like:
> >
> > SELECT *
> > INTO [ArchiveDBName].dbo.[TableName]
> > FROM dbo.[OriginalDBName]
> > WHERE [DateStamp] < '1/1/2006'
> >
> > And to delete the records from the original table:
> >
> > DELETE FROM dbo.[OriginalDBName]
> > WHERE [DateStamp] < '1/1/2006'
> >
> > However, it was not clear from you post if you have access to Query Analyzer.
> >
> > Lucas
> >
> >
> > "mattdaddym@.gmail.com" wrote:
> >
> > > Hi all,
> > >
> > > I have a database I maintain that has grown quite large. The part of it
> > > I am interested in, is one paticular table that logs the history of
> > > certain high volume "events". I have events back to 2002, and the
> > > database is almost 3 Gigs. I rarely need to query more than 6 months
> > > worth. Here is what I would like to do.
> > >
> > > I'd like to split the database, and create an archive database. I want
> > > to move everything before 2006 to this new database. Now, I know I can
> > > do a complete backup, and then delete the stuff I don't need, but I
> > > wanted to know if there is a way to import just the dates I need from
> > > the current database. Of course, there is a timedate field to key off
> > > of.
> > >
> > > I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
> > > 2003 Server.
> > >
> > > Thanks in advance.
> > >
> > >
>|||That is great. Thank you!
Lucas Kartawidjaja wrote:
> Actually with the SELECT INTO statement the beauty of it is that you don't
> need to create the table first. SELECT INTO will create it for you the table
> structure will be the same as the original table.
> Lucas
> "mattdaddym@.gmail.com" wrote:
> > I do have access to query analyzer. I was hoping for a way to do it in
> > the GUI since it creats the tables automatically when you do an import.
> > I don't know for sure, but I will assume if I use your command that I
> > will need to set the table up first. Not a big deal, though. I guess
> > I'm just being lazy. Thank you!
> > Lucas Kartawidjaja wrote:
> > > Hi there
> > >
> > > There are several ways to do this. You can try to use DTS to move the data
> > > over. Or you can use query analyzer. If you can use Query Analyzer, you can
> > > actually use a query something like:
> > >
> > > SELECT *
> > > INTO [ArchiveDBName].dbo.[TableName]
> > > FROM dbo.[OriginalDBName]
> > > WHERE [DateStamp] < '1/1/2006'
> > >
> > > And to delete the records from the original table:
> > >
> > > DELETE FROM dbo.[OriginalDBName]
> > > WHERE [DateStamp] < '1/1/2006'
> > >
> > > However, it was not clear from you post if you have access to Query Analyzer.
> > >
> > > Lucas
> > >
> > >
> > > "mattdaddym@.gmail.com" wrote:
> > >
> > > > Hi all,
> > > >
> > > > I have a database I maintain that has grown quite large. The part of it
> > > > I am interested in, is one paticular table that logs the history of
> > > > certain high volume "events". I have events back to 2002, and the
> > > > database is almost 3 Gigs. I rarely need to query more than 6 months
> > > > worth. Here is what I would like to do.
> > > >
> > > > I'd like to split the database, and create an archive database. I want
> > > > to move everything before 2006 to this new database. Now, I know I can
> > > > do a complete backup, and then delete the stuff I don't need, but I
> > > > wanted to know if there is a way to import just the dates I need from
> > > > the current database. Of course, there is a timedate field to key off
> > > > of.
> > > >
> > > > I am using the GUI to do this in Enterprise Manager SQL 2000, Windows
> > > > 2003 Server.
> > > >
> > > > Thanks in advance.
> > > >
> > > >
> >
> >

Database Healthchecks

Hi,
Does anyone have any good suggestions for things to look at/run etc. in a
database healthcheck?
It's purely the database I'm interested in, not the server.
Many thanks.
Hi Chappers
There are a number of things you can do.
Look at the SQL Error logs and Windows Event logs and look for any
unexpected messages.
Run a regular 'DBCC CHECKDB' and check the output.
Look at the various ways you can use profiler and perfmon to get more
information on the health of your database. Here are links to two good
articles.
Perfmon Tips
http://www.sql-server-performance.co...nitor_tips.asp
Profiler Tips
http://www.sql-server-performance.co...filer_tips.asp
Make sure your tables are not getting too fragmented. If your database is
not that large, you can just set up a full maintenence plan (this will do the
dbcc's as well).
If it's too large (ie maint plan takes a couple of hours or more to run).
You can use dbcc showcontig (see BOL) to check table fragmentation and
schedule index rebuilds where applicable.
Hope this helps
John
"Chappers" wrote:

> Hi,
> Does anyone have any good suggestions for things to look at/run etc. in a
> database healthcheck?
> It's purely the database I'm interested in, not the server.
> Many thanks.
|||Thanks John.
I have my own list of stuff to do and deliberately left the question open to
see what other people came up with so I could see what I'd missed.
Many thanks for taking the time to reply.
Paul
"John Bandettini" wrote:
[vbcol=seagreen]
> Hi Chappers
> There are a number of things you can do.
> Look at the SQL Error logs and Windows Event logs and look for any
> unexpected messages.
> Run a regular 'DBCC CHECKDB' and check the output.
> Look at the various ways you can use profiler and perfmon to get more
> information on the health of your database. Here are links to two good
> articles.
> Perfmon Tips
> http://www.sql-server-performance.co...nitor_tips.asp
> Profiler Tips
> http://www.sql-server-performance.co...filer_tips.asp
> Make sure your tables are not getting too fragmented. If your database is
> not that large, you can just set up a full maintenence plan (this will do the
> dbcc's as well).
> If it's too large (ie maint plan takes a couple of hours or more to run).
> You can use dbcc showcontig (see BOL) to check table fragmentation and
> schedule index rebuilds where applicable.
> Hope this helps
> John
> "Chappers" wrote:
|||Regarding index fragmentation - don't just rebuild indexes because they have
fragmentation - whether it will have any effect on performance depends on
the queries you're running. Also, rebuilding an index takes and additional
1.2x the size of the index and makes the index offline for the duration of
the operation - you should consider using DBCC INDEXDEFRAG instead. More
info on all of this can be found in our whitepaper below:
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chappers" <Chappers@.discussions.microsoft.com> wrote in message
news:29D074BE-1443-467A-B2F7-0A28691370DC@.microsoft.com...
> Thanks John.
> I have my own list of stuff to do and deliberately left the question open
to[vbcol=seagreen]
> see what other people came up with so I could see what I'd missed.
> Many thanks for taking the time to reply.
> Paul
> "John Bandettini" wrote:
is[vbcol=seagreen]
do the[vbcol=seagreen]
run).[vbcol=seagreen]
in a[vbcol=seagreen]

Database Healthchecks

Hi,
Does anyone have any good suggestions for things to look at/run etc. in a
database healthcheck?
It's purely the database I'm interested in, not the server.
Many thanks.Hi Chappers
There are a number of things you can do.
Look at the SQL Error logs and Windows Event logs and look for any
unexpected messages.
Run a regular 'DBCC CHECKDB' and check the output.
Look at the various ways you can use profiler and perfmon to get more
information on the health of your database. Here are links to two good
articles.
Perfmon Tips
http://www.sql-server-performance.com/performance_monitor_tips.asp
Profiler Tips
http://www.sql-server-performance.com/sql_server_profiler_tips.asp
Make sure your tables are not getting too fragmented. If your database is
not that large, you can just set up a full maintenence plan (this will do the
dbcc's as well).
If it's too large (ie maint plan takes a couple of hours or more to run).
You can use dbcc showcontig (see BOL) to check table fragmentation and
schedule index rebuilds where applicable.
Hope this helps
John
"Chappers" wrote:
> Hi,
> Does anyone have any good suggestions for things to look at/run etc. in a
> database healthcheck?
> It's purely the database I'm interested in, not the server.
> Many thanks.|||Thanks John.
I have my own list of stuff to do and deliberately left the question open to
see what other people came up with so I could see what I'd missed.
Many thanks for taking the time to reply.
Paul
"John Bandettini" wrote:
> Hi Chappers
> There are a number of things you can do.
> Look at the SQL Error logs and Windows Event logs and look for any
> unexpected messages.
> Run a regular 'DBCC CHECKDB' and check the output.
> Look at the various ways you can use profiler and perfmon to get more
> information on the health of your database. Here are links to two good
> articles.
> Perfmon Tips
> http://www.sql-server-performance.com/performance_monitor_tips.asp
> Profiler Tips
> http://www.sql-server-performance.com/sql_server_profiler_tips.asp
> Make sure your tables are not getting too fragmented. If your database is
> not that large, you can just set up a full maintenence plan (this will do the
> dbcc's as well).
> If it's too large (ie maint plan takes a couple of hours or more to run).
> You can use dbcc showcontig (see BOL) to check table fragmentation and
> schedule index rebuilds where applicable.
> Hope this helps
> John
> "Chappers" wrote:
> > Hi,
> >
> > Does anyone have any good suggestions for things to look at/run etc. in a
> > database healthcheck?
> >
> > It's purely the database I'm interested in, not the server.
> >
> > Many thanks.|||Regarding index fragmentation - don't just rebuild indexes because they have
fragmentation - whether it will have any effect on performance depends on
the queries you're running. Also, rebuilding an index takes and additional
1.2x the size of the index and makes the index offline for the duration of
the operation - you should consider using DBCC INDEXDEFRAG instead. More
info on all of this can be found in our whitepaper below:
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
Regards
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chappers" <Chappers@.discussions.microsoft.com> wrote in message
news:29D074BE-1443-467A-B2F7-0A28691370DC@.microsoft.com...
> Thanks John.
> I have my own list of stuff to do and deliberately left the question open
to
> see what other people came up with so I could see what I'd missed.
> Many thanks for taking the time to reply.
> Paul
> "John Bandettini" wrote:
> > Hi Chappers
> >
> > There are a number of things you can do.
> >
> > Look at the SQL Error logs and Windows Event logs and look for any
> > unexpected messages.
> >
> > Run a regular 'DBCC CHECKDB' and check the output.
> >
> > Look at the various ways you can use profiler and perfmon to get more
> > information on the health of your database. Here are links to two good
> > articles.
> >
> > Perfmon Tips
> >
> > http://www.sql-server-performance.com/performance_monitor_tips.asp
> >
> > Profiler Tips
> >
> > http://www.sql-server-performance.com/sql_server_profiler_tips.asp
> >
> > Make sure your tables are not getting too fragmented. If your database
is
> > not that large, you can just set up a full maintenence plan (this will
do the
> > dbcc's as well).
> > If it's too large (ie maint plan takes a couple of hours or more to
run).
> > You can use dbcc showcontig (see BOL) to check table fragmentation and
> > schedule index rebuilds where applicable.
> >
> > Hope this helps
> >
> > John
> >
> > "Chappers" wrote:
> >
> > > Hi,
> > >
> > > Does anyone have any good suggestions for things to look at/run etc.
in a
> > > database healthcheck?
> > >
> > > It's purely the database I'm interested in, not the server.
> > >
> > > Many thanks.

Database Healthchecks

Hi,
Does anyone have any good suggestions for things to look at/run etc. in a
database healthcheck?
It's purely the database I'm interested in, not the server.
Many thanks.Hi Chappers
There are a number of things you can do.
Look at the SQL Error logs and Windows Event logs and look for any
unexpected messages.
Run a regular 'DBCC CHECKDB' and check the output.
Look at the various ways you can use profiler and perfmon to get more
information on the health of your database. Here are links to two good
articles.
Perfmon Tips
http://www.sql-server-performance.c...onitor_tips.asp
Profiler Tips
http://www.sql-server-performance.c...ofiler_tips.asp
Make sure your tables are not getting too fragmented. If your database is
not that large, you can just set up a full maintenence plan (this will do th
e
dbcc's as well).
If it's too large (ie maint plan takes a couple of hours or more to run).
You can use dbcc showcontig (see BOL) to check table fragmentation and
schedule index rebuilds where applicable.
Hope this helps
John
"Chappers" wrote:

> Hi,
> Does anyone have any good suggestions for things to look at/run etc. in a
> database healthcheck?
> It's purely the database I'm interested in, not the server.
> Many thanks.|||Thanks John.
I have my own list of stuff to do and deliberately left the question open to
see what other people came up with so I could see what I'd missed.
Many thanks for taking the time to reply.
Paul
"John Bandettini" wrote:
[vbcol=seagreen]
> Hi Chappers
> There are a number of things you can do.
> Look at the SQL Error logs and Windows Event logs and look for any
> unexpected messages.
> Run a regular 'DBCC CHECKDB' and check the output.
> Look at the various ways you can use profiler and perfmon to get more
> information on the health of your database. Here are links to two good
> articles.
> Perfmon Tips
> http://www.sql-server-performance.c...onitor_tips.asp
> Profiler Tips
> http://www.sql-server-performance.c...ofiler_tips.asp
> Make sure your tables are not getting too fragmented. If your database is
> not that large, you can just set up a full maintenence plan (this will do
the
> dbcc's as well).
> If it's too large (ie maint plan takes a couple of hours or more to run).
> You can use dbcc showcontig (see BOL) to check table fragmentation and
> schedule index rebuilds where applicable.
> Hope this helps
> John
> "Chappers" wrote:
>|||Regarding index fragmentation - don't just rebuild indexes because they have
fragmentation - whether it will have any effect on performance depends on
the queries you're running. Also, rebuilding an index takes and additional
1.2x the size of the index and makes the index offline for the duration of
the operation - you should consider using DBCC INDEXDEFRAG instead. More
info on all of this can be found in our whitepaper below:
http://www.microsoft.com/technet/pr...n/ss2kidbp.mspx
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chappers" <Chappers@.discussions.microsoft.com> wrote in message
news:29D074BE-1443-467A-B2F7-0A28691370DC@.microsoft.com...
> Thanks John.
> I have my own list of stuff to do and deliberately left the question open
to[vbcol=seagreen]
> see what other people came up with so I could see what I'd missed.
> Many thanks for taking the time to reply.
> Paul
> "John Bandettini" wrote:
>
is[vbcol=seagreen]
do the[vbcol=seagreen]
run).[vbcol=seagreen]
in a[vbcol=seagreen]

Database Engine Tuning Advisor and Small Workload Files

Hi all,
If I'm interested in tuning a single stored procedure, does the number
of executions of the Sproc in the workload make any difference to the
quality of the DETA?
For example, if I setup a trace in SQL Profiler and executed the sproc
10 times, would it make a difference as compared to a trace where the
procedure were executed only once?
Many thanks
SimonIt would if the stored procedure has parameters and you ran it with a
representative mix of parameter values.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Simon Harvey" <nothanks@.hotmail.com> wrote in message
news:OIHTCWOJHHA.1424@.TK2MSFTNGP04.phx.gbl...
> Hi all,
> If I'm interested in tuning a single stored procedure, does the number of
> executions of the Sproc in the workload make any difference to the quality
> of the DETA?
> For example, if I setup a trace in SQL Profiler and executed the sproc 10
> times, would it make a difference as compared to a trace where the
> procedure were executed only once?
> Many thanks
> Simon

Database Engine Tuning Advisor and Small Workload Files

Hi all,
If I'm interested in tuning a single stored procedure, does the number
of executions of the Sproc in the workload make any difference to the
quality of the DETA?
For example, if I setup a trace in SQL Profiler and executed the sproc
10 times, would it make a difference as compared to a trace where the
procedure were executed only once?
Many thanks
Simon
It would if the stored procedure has parameters and you ran it with a
representative mix of parameter values.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Simon Harvey" <nothanks@.hotmail.com> wrote in message
news:OIHTCWOJHHA.1424@.TK2MSFTNGP04.phx.gbl...
> Hi all,
> If I'm interested in tuning a single stored procedure, does the number of
> executions of the Sproc in the workload make any difference to the quality
> of the DETA?
> For example, if I setup a trace in SQL Profiler and executed the sproc 10
> times, would it make a difference as compared to a trace where the
> procedure were executed only once?
> Many thanks
> Simon
sql

Database Engine Tuning Advisor and Small Workload Files

Hi all,
If I'm interested in tuning a single stored procedure, does the number
of executions of the Sproc in the workload make any difference to the
quality of the DETA?
For example, if I setup a trace in SQL Profiler and executed the sproc
10 times, would it make a difference as compared to a trace where the
procedure were executed only once?
Many thanks
SimonIt would if the stored procedure has parameters and you ran it with a
representative mix of parameter values.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Simon Harvey" <nothanks@.hotmail.com> wrote in message
news:OIHTCWOJHHA.1424@.TK2MSFTNGP04.phx.gbl...
> Hi all,
> If I'm interested in tuning a single stored procedure, does the number of
> executions of the Sproc in the workload make any difference to the quality
> of the DETA?
> For example, if I setup a trace in SQL Profiler and executed the sproc 10
> times, would it make a difference as compared to a trace where the
> procedure were executed only once?
> Many thanks
> Simon

Database Documentation

I would be interested in hearing what tools people have used to document the
business uses of tables in a database? I have looked at the meta data
services that comes with SQL Server, and while it looks like a good tool, I
do not think that it fits particularly well with what I am looking to
accomplish. I would like to have some documentation that outlines the
business uses of/business rules for each table in the database. Almost an
ERD, but something that discusses/shows information about the business model
that the database/system(s) were constructed to support.
Any advice is appreciated!
TimHello Tim,
This might not be what you are looking for but maybe it can be. I've started
a project which is intended to help people with their network documentation.
The output is to Microsoft word.
The project has two files, one for documenting Servers in general and one
for documenting SQL-Servers. I've just started with the SQL version so there
are a lot of things that can be added.
If you are interested in the project you can find information here:
http://sydi.sourceforge.net
If you want to add feature requests you can do so here:
http://sourceforge.net/tracker/?group_id=116471&atid=674897
Best regards
Patrick
"TimS" <timstspry@.msn.com(donotspam)> wrote in message
news:77AD57C8-C893-41D7-B200-38435DB2D11A@.microsoft.com...
> I would be interested in hearing what tools people have used to document
the
> business uses of tables in a database? I have looked at the meta data
> services that comes with SQL Server, and while it looks like a good tool,
I
> do not think that it fits particularly well with what I am looking to
> accomplish. I would like to have some documentation that outlines the
> business uses of/business rules for each table in the database. Almost an
> ERD, but something that discusses/shows information about the business
model
> that the database/system(s) were constructed to support.
> Any advice is appreciated!
> Tim|||Hi Tim,
Here is what we have done. In our database we have two "extra tables" One
that describes the tables and one that describes individual fields
(columns). The fields table has a foreign key back to the tables table so
that fields can be associated with their proper table. In those tables we
have columns that are used to describe the individual tables and fields.
Things like business rules, uses etc. We then have a set of web pages that
connect to an empty version of the database that has only this meta data
information in it. Everyone can use them to view and update this
information. Each time a new version of the DB comes out we have an
automated process that creates a new empty DB, copies the two tables of meta
data from the existing DB and then updates the metadata tables with the
updates to the schema (updated tables & colums). The existing DB then gets
replaced with the updated DB and the web pages now use this.
Wayne
"TimS" <timstspry@.msn.com(donotspam)> wrote in message
news:77AD57C8-C893-41D7-B200-38435DB2D11A@.microsoft.com...
>I would be interested in hearing what tools people have used to document
>the
> business uses of tables in a database? I have looked at the meta data
> services that comes with SQL Server, and while it looks like a good tool,
> I
> do not think that it fits particularly well with what I am looking to
> accomplish. I would like to have some documentation that outlines the
> business uses of/business rules for each table in the database. Almost an
> ERD, but something that discusses/shows information about the business
> model
> that the database/system(s) were constructed to support.
> Any advice is appreciated!
> Tim|||SchemaToDoc (http://www.schematodoc.com) lets you annotate the tables and
fields in your database. It then lets you export the structure of your
database (tables, fields, indexes, check constraints, foreign key
constraints, and triggers) as well as your annotations to a Word document.
"Patrick Ogenstad" <patrick.ogenstad@.netsafe.se> wrote in message
news:uoeqjdgoEHA.1272@.TK2MSFTNGP09.phx.gbl...
> Hello Tim,
>
> This might not be what you are looking for but maybe it can be. I've
started
> a project which is intended to help people with their network
documentation.
> The output is to Microsoft word.
>
> The project has two files, one for documenting Servers in general and one
> for documenting SQL-Servers. I've just started with the SQL version so
there
> are a lot of things that can be added.
>
> If you are interested in the project you can find information here:
> http://sydi.sourceforge.net
>
> If you want to add feature requests you can do so here:
> http://sourceforge.net/tracker/?group_id=116471&atid=674897
>
> Best regards
> Patrick
>
> "TimS" <timstspry@.msn.com(donotspam)> wrote in message
> news:77AD57C8-C893-41D7-B200-38435DB2D11A@.microsoft.com...
> > I would be interested in hearing what tools people have used to document
> the
> > business uses of tables in a database? I have looked at the meta data
> > services that comes with SQL Server, and while it looks like a good
tool,
> I
> > do not think that it fits particularly well with what I am looking to
> > accomplish. I would like to have some documentation that outlines the
> > business uses of/business rules for each table in the database. Almost
an
> > ERD, but something that discusses/shows information about the business
> model
> > that the database/system(s) were constructed to support.
> >
> > Any advice is appreciated!
> >
> > Tim
>

Database Documentation

I would be interested in hearing what tools people have used to document the
business uses of tables in a database? I have looked at the meta data
services that comes with SQL Server, and while it looks like a good tool, I
do not think that it fits particularly well with what I am looking to
accomplish. I would like to have some documentation that outlines the
business uses of/business rules for each table in the database. Almost an
ERD, but something that discusses/shows information about the business model
that the database/system(s) were constructed to support.
Any advice is appreciated!
Tim
Hello Tim,
This might not be what you are looking for but maybe it can be. I've started
a project which is intended to help people with their network documentation.
The output is to Microsoft word.
The project has two files, one for documenting Servers in general and one
for documenting SQL-Servers. I've just started with the SQL version so there
are a lot of things that can be added.
If you are interested in the project you can find information here:
http://sydi.sourceforge.net
If you want to add feature requests you can do so here:
http://sourceforge.net/tracker/?grou...71&atid=674897
Best regards
Patrick
"TimS" <timstspry@.msn.com(donotspam)> wrote in message
news:77AD57C8-C893-41D7-B200-38435DB2D11A@.microsoft.com...
> I would be interested in hearing what tools people have used to document
the
> business uses of tables in a database? I have looked at the meta data
> services that comes with SQL Server, and while it looks like a good tool,
I
> do not think that it fits particularly well with what I am looking to
> accomplish. I would like to have some documentation that outlines the
> business uses of/business rules for each table in the database. Almost an
> ERD, but something that discusses/shows information about the business
model
> that the database/system(s) were constructed to support.
> Any advice is appreciated!
> Tim
|||Hi Tim,
Here is what we have done. In our database we have two "extra tables" One
that describes the tables and one that describes individual fields
(columns). The fields table has a foreign key back to the tables table so
that fields can be associated with their proper table. In those tables we
have columns that are used to describe the individual tables and fields.
Things like business rules, uses etc. We then have a set of web pages that
connect to an empty version of the database that has only this meta data
information in it. Everyone can use them to view and update this
information. Each time a new version of the DB comes out we have an
automated process that creates a new empty DB, copies the two tables of meta
data from the existing DB and then updates the metadata tables with the
updates to the schema (updated tables & colums). The existing DB then gets
replaced with the updated DB and the web pages now use this.
Wayne
"TimS" <timstspry@.msn.com(donotspam)> wrote in message
news:77AD57C8-C893-41D7-B200-38435DB2D11A@.microsoft.com...
>I would be interested in hearing what tools people have used to document
>the
> business uses of tables in a database? I have looked at the meta data
> services that comes with SQL Server, and while it looks like a good tool,
> I
> do not think that it fits particularly well with what I am looking to
> accomplish. I would like to have some documentation that outlines the
> business uses of/business rules for each table in the database. Almost an
> ERD, but something that discusses/shows information about the business
> model
> that the database/system(s) were constructed to support.
> Any advice is appreciated!
> Tim
|||SchemaToDoc (http://www.schematodoc.com) lets you annotate the tables and
fields in your database. It then lets you export the structure of your
database (tables, fields, indexes, check constraints, foreign key
constraints, and triggers) as well as your annotations to a Word document.
"Patrick Ogenstad" <patrick.ogenstad@.netsafe.se> wrote in message
news:uoeqjdgoEHA.1272@.TK2MSFTNGP09.phx.gbl...
> Hello Tim,
>
> This might not be what you are looking for but maybe it can be. I've
started
> a project which is intended to help people with their network
documentation.
> The output is to Microsoft word.
>
> The project has two files, one for documenting Servers in general and one
> for documenting SQL-Servers. I've just started with the SQL version so
there[vbcol=seagreen]
> are a lot of things that can be added.
>
> If you are interested in the project you can find information here:
> http://sydi.sourceforge.net
>
> If you want to add feature requests you can do so here:
> http://sourceforge.net/tracker/?grou...71&atid=674897
>
> Best regards
> Patrick
>
> "TimS" <timstspry@.msn.com(donotspam)> wrote in message
> news:77AD57C8-C893-41D7-B200-38435DB2D11A@.microsoft.com...
> the
tool,[vbcol=seagreen]
> I
an
> model
>