query analyzer

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

segue - 06 Mar 2008 18:31 GMT

I have disc 1 and 2 for sqlserver 2005 enterprise edition
which pulls up browser contents when I run autoplay.

All I think I want is to add query analyzer to my local client installation.

How can I install query analyzer to an sqlserver2005 client installation?

The following are the disc contents:

SQL Server™ 2005 Standard Edition, Disc 1 (English)

SQL Server™ 2005 Standard Edition, Disc 2 (English)

Is there a better tool than query analyzer for importing access data to a
disparate sqlserver2005 db?

Much thanks.

Reply to this Message

jason - 06 Mar 2008 19:52 GMT

Use disk one and install the client tools. However, it is not QA anymore. It
is called SQL Server management studio and can be started by running SQLWB.

Signature

Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio

>I have disc 1 and 2 for sqlserver 2005 enterprise edition
> which pulls up browser contents when I run autoplay.
[quoted text clipped - 14 lines]
>
> Much thanks.

Reply to this Message

segue - 06 Mar 2008 21:53 GMT

Thanks so much for the heads up.

So, I'm currently trying to use management studio to connect to an odbc link
or databases - I've been connected to an odbc database in visual studio using
(tools
connect to database).

I've noticed in the SQL management studio a popup (connect to database
engine).

I don't think connect to database engine is what I need - suggestions
appreciated on using sql ms to connect to a db that is connected with VS
using connect to a database which connects to an odbc connection.

> Use disk one and install the client tools. However, it is not QA anymore. It
> is called SQL Server management studio and can be started by running SQLWB.
[quoted text clipped - 17 lines]
> >
> > Much thanks.

Reply to this Message

Russell Fields - 06 Mar 2008 21:10 GMT

segue,

The better tool than Query Analyzer for importing Access data to a SQL
Server DB is SSIS. (SQL Server Integration Services) However, the SQL
Server Management Studio has an Import Data wizard that wraps up that
functionality for you without requiring learning SSIS. (Provided your needs
are not complex.)

From SSMS, right click on a database, select Tasks / Import Data ... and
follow the dialogues.

RLF

>I have disc 1 and 2 for sqlserver 2005 enterprise edition
> which pulls up browser contents when I run autoplay.
[quoted text clipped - 14 lines]
>
> Much thanks.

Reply to this Message

segue - 07 Mar 2008 00:40 GMT

Hi - got it. Is it best to just create a db under the master db when
copying or transferring data? I've had some results where just one row is
copied successfully then the ssis import exits and goes to the next table.
Is there a log?

When importing data between disparate db's do you recommend using an sql
statement or this sql server import wizard.

Examples of an sql transfer of data with SSIS appreciated.

Much Thanks.

> segue,
>
[quoted text clipped - 27 lines]
> >
> > Much thanks.

Reply to this Message

Russell Fields - 12 Mar 2008 13:54 GMT

segue,

If you have a single Access database that you want to distribute to multiple
SQL databases, I would suggest creating a single staging database to bring
all of the Access data into. Then you can use T-SQL to distribute the data
to the other databases.

FWIW,
RLF

> Hi - got it. Is it best to just create a db under the master db when
> copying or transferring data? I've had some results where just one row is
[quoted text clipped - 42 lines]
>> >
>> > Much thanks.

Reply to this Message