Is it possible to export a View to Excel in MS SQL 2000 ?

Hi all,

In MS SQL Management Console I can right-click on any Table and I have
the option All Tasks > Export Data where I can export the table to
Excel. In a View however this isn't there. I have many views I want
to simply export to Excel, but the only way I've found to do it is
creating an ODBC connection to the MS SQL database from MS Access,
linking the Views to Access Tables, and exporting from Access. surely
there's someway to export a View to Excel within MS SQL easily like
exporting a table...

Thanks --

AlexIf this is a one-off task, the Import/Export Wizard can export to a
..xls. If you need to run it regularly, then you can save the DTS
package created by the wizard, and modify it as required.

Simon

Is it better to run maintenance sequentially or pralell

we have a maintenance process which does various dbcc maintenance tasks such
as dbreindex, indexdefrag and updateusage. This process can take over 4
hours for some of the databases.
Is there any drawback to running these maintenance processes parallel on all
databases or is it better to run them sequentially?
Hi
There is no issue with running them in parallel, but, can your disk
subsystem keep up? These taks are very IO intensive.
If they run in parallel, the sum of all the jobs might decrease, but each
individual job will take longer to complete.
Regards
Mike
"DBA72" wrote:

> we have a maintenance process which does various dbcc maintenance tasks such
> as dbreindex, indexdefrag and updateusage. This process can take over 4
> hours for some of the databases.
> Is there any drawback to running these maintenance processes parallel on all
> databases or is it better to run them sequentially?

Is it better to run maintenance sequentially or pralell

we have a maintenance process which does various dbcc maintenance tasks such
as dbreindex, indexdefrag and updateusage. This process can take over 4
hours for some of the databases.
Is there any drawback to running these maintenance processes parallel on all
databases or is it better to run them sequentially?Hi
There is no issue with running them in parallel, but, can your disk
subsystem keep up? These taks are very IO intensive.
If they run in parallel, the sum of all the jobs might decrease, but each
individual job will take longer to complete.
Regards
Mike
"DBA72" wrote:

> we have a maintenance process which does various dbcc maintenance tasks su
ch
> as dbreindex, indexdefrag and updateusage. This process can take over 4
> hours for some of the databases.
> Is there any drawback to running these maintenance processes parallel on a
ll
> databases or is it better to run them sequentially?

Is it better to run maintenance sequentially or pralell

we have a maintenance process which does various dbcc maintenance tasks such
as dbreindex, indexdefrag and updateusage. This process can take over 4
hours for some of the databases.
Is there any drawback to running these maintenance processes parallel on all
databases or is it better to run them sequentially?Hi
There is no issue with running them in parallel, but, can your disk
subsystem keep up? These taks are very IO intensive.
If they run in parallel, the sum of all the jobs might decrease, but each
individual job will take longer to complete.
Regards
Mike
"DBA72" wrote:
> we have a maintenance process which does various dbcc maintenance tasks such
> as dbreindex, indexdefrag and updateusage. This process can take over 4
> hours for some of the databases.
> Is there any drawback to running these maintenance processes parallel on all
> databases or is it better to run them sequentially?