Monday, March 12, 2012
Quick SQL Server version question
Personal Edition on the same NT 4.0 Client machine ? SQL
Server 7.0 Desktop Edition is already installed.
Thanks.Jennifer,
Yes.While installing SQL2000, select the option to install a named
instance.Thus SQL7 becomes the default instance and SQL2000, the named
instance.After the SQL2000 setup, all gui tools would be of the latest
version.
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Jennifer" <jflin@.hotmail.com> wrote in message
news:023401c365a7$5821cda0$a101280a@.phx.gbl...
> Can I run SQL Server 7.0 Desktop and SQL Server 2000
> Personal Edition on the same NT 4.0 Client machine ? SQL
> Server 7.0 Desktop Edition is already installed.
> Thanks.|||What my concern is; When you connect to an SQL Server 7.0
server from SQL Server 2000 computer and modify/save DTS
packages, It will not work on the SQL Server 7.0 server
anymore. I keep forgetting that fact and modifying DTS
packages on SQL Server 7.0 servers. I want to avoid that.
How could this work on a client computer with both
versions installed ?
Thanks....
>--Original Message--
>Can I run SQL Server 7.0 Desktop and SQL Server 2000
>Personal Edition on the same NT 4.0 Client machine ? SQL
>Server 7.0 Desktop Edition is already installed.
>Thanks.
>.
>
Quick SQL Server 7.0 index question
need as a backend for the various internal desktop/web applications I write.
I haven't ever had the time to get seriously involved with internal workings
of SQL Server and we are far too small to employ a DBA.
With any new application performance isn't a problem as the number of
records is very low. Over the life of the application the number of records
obviously increases and performance can start to suffer. My normal cure is
to use the Query Analyzer to suggest and implement indexes that normally get
things back up to speed.
I was wondering whether SQL Server automatically keeps the created indexes
up to date or do I need to be doing anything else either manually or as a
scheduled job? The databases all have auto create statistics and auto update
statistics enabled.
Any pointers gratefully received
Thanks
AlanEnsure the indexes are periodically defragged. Either by a maintenance
plan or DBCC DBReindex. See BOL for details.|||xyz (someone@.somewhere.com) writes:
> I was wondering whether SQL Server automatically keeps the created
> indexes up to date or do I need to be doing anything else either
> manually or as a scheduled job? The databases all have auto create
> statistics and auto update statistics enabled.
What can happen with indexes - as well with the data pages them selves -
is that they can get fragmented. Essentially this means that that the
data is not stored as compactly as it could be. Recall that SQL Server
stores data on pages of 8192 bytes size. And these pages are gathered
eight by eight in extents. One extent is usually only for one table
(but the first page for a table goes into a mixed extent.) If there are
lots of insertions and deletions, you can end up with extents with
only some single rows in them. This leads to that SQL Server will have
to perform more disk reads to get the same amount of data.
The easiest way to approach this is to set up a maintenance job that
performs a DBCC DBREINDEX on all tables. (Although this is not the
most effecient. Tables with little fragmentation are best left alone.)
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns96005592901DYazorman@.127.0.0.1...
> xyz (someone@.somewhere.com) writes:
> > I was wondering whether SQL Server automatically keeps the created
> > indexes up to date or do I need to be doing anything else either
> > manually or as a scheduled job? The databases all have auto create
> > statistics and auto update statistics enabled.
> What can happen with indexes - as well with the data pages them selves -
> is that they can get fragmented. Essentially this means that that the
> data is not stored as compactly as it could be. Recall that SQL Server
> stores data on pages of 8192 bytes size. And these pages are gathered
> eight by eight in extents. One extent is usually only for one table
> (but the first page for a table goes into a mixed extent.) If there are
> lots of insertions and deletions, you can end up with extents with
> only some single rows in them. This leads to that SQL Server will have
> to perform more disk reads to get the same amount of data.
> The easiest way to approach this is to set up a maintenance job that
> performs a DBCC DBREINDEX on all tables. (Although this is not the
> most effecient. Tables with little fragmentation are best left alone.)
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp
Thanks to both you and louis for the imformation.