Other IDE tools

what are some other IDE tools to use with sql server 2000 and 2005? I like
query analyzer a lot and am not crazy about EM or SQL Workbench (or whatever
it is called these days).
What does this community use when you are not using QA, EM or Workbench? I
like to type in T-SQL rather than be using the GUI (but that doesn't mean I
want to use isql/osql :-)
I use QA almost exclusively, and will probably use SQL Server Management
Studio (formally known as SQL Workbench) in SQL Server 2005 exclusively.
I'm happy with both.
BG, SQL Server MVP
www.SolidQualityLearning.com
"Kyle Adams" <kadam@.aol.spammersbeware.com> wrote in message
news:udAs5PHjEHA.2556@.TK2MSFTNGP10.phx.gbl...
> what are some other IDE tools to use with sql server 2000 and 2005? I
like
> query analyzer a lot and am not crazy about EM or SQL Workbench (or
whatever
> it is called these days).
> What does this community use when you are not using QA, EM or Workbench?
I
> like to type in T-SQL rather than be using the GUI (but that doesn't mean
I
> want to use isql/osql :-)
>
>
|||I think Management Studio (the IDE formerly known as SQL WorkBench) is going
to turn out very useful, albeit missing features that some users are willing
to bypass upgrading for (e.g. open table). Here are some alternative
management tools you can investigate:
http://www.aspfaq.com/2442
http://www.aspfaq.com/
(Reverse address to reply.)
"Kyle Adams" <kadam@.aol.spammersbeware.com> wrote in message
news:udAs5PHjEHA.2556@.TK2MSFTNGP10.phx.gbl...
> what are some other IDE tools to use with sql server 2000 and 2005? I
like
> query analyzer a lot and am not crazy about EM or SQL Workbench (or
whatever
> it is called these days).
> What does this community use when you are not using QA, EM or Workbench?
I
> like to type in T-SQL rather than be using the GUI (but that doesn't mean
I
> want to use isql/osql :-)
>
>
|||Kyle Adams wrote:
> what are some other IDE tools to use with sql server 2000 and 2005?
> I like query analyzer a lot and am not crazy about EM or SQL
> Workbench (or whatever it is called these days).
> What does this community use when you are not using QA, EM or
> Workbench? I like to type in T-SQL rather than be using the GUI (but
> that doesn't mean I want to use isql/osql :-)
Imceda Software makes a really nice IDE tool (www.imceda.com)
David G.
|||Hi Kyle,

> what are some other IDE tools to use with sql server 2000 and 2005? I
like
> query analyzer a lot and am not crazy about EM or SQL Workbench (or
whatever
> it is called these days).
> What does this community use when you are not using QA, EM or Workbench?
I
> like to type in T-SQL rather than be using the GUI (but that doesn't mean
I
> want to use isql/osql :-)
You might want to take a look at our Database Workbench -
works with MSDE, 7 and 2000 as well as some other database
engines.
It has GUI tools for table-editting, but no diagramming tools.
In two weeks, we will be releasing a new version with new features
and many GUI improvements.
Check it out at www.upscene.com
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com
|||Give Query Analyzer Tool from our website a spin. It's a free tool inclined
towards helping you analyze query plans better.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backups? Use MiniSQLBackup Lite, free!
"Kyle Adams" <kadam@.aol.spammersbeware.com> wrote in message
news:udAs5PHjEHA.2556@.TK2MSFTNGP10.phx.gbl...
> what are some other IDE tools to use with sql server 2000 and 2005? I
like
> query analyzer a lot and am not crazy about EM or SQL Workbench (or
whatever
> it is called these days).
> What does this community use when you are not using QA, EM or Workbench?
I
> like to type in T-SQL rather than be using the GUI (but that doesn't mean
I
> want to use isql/osql :-)
>
>
|||I'd give SQL IDE from imceda a big look at.
http://www.imceda.com
Bryan
"Kyle Adams" <kadam@.aol.spammersbeware.com> wrote in message
news:udAs5PHjEHA.2556@.TK2MSFTNGP10.phx.gbl...
> what are some other IDE tools to use with sql server 2000 and 2005? I
like
> query analyzer a lot and am not crazy about EM or SQL Workbench (or
whatever
> it is called these days).
> What does this community use when you are not using QA, EM or Workbench?
I
> like to type in T-SQL rather than be using the GUI (but that doesn't mean
I
> want to use isql/osql :-)
>
>

OS and SQL Server installed on seperate drives.

We have a server with one IDE drive which is where the OS
in located. We have recently purchased a SCSI drive and
intend on installing SQL Server 2000 on it. Is anyone
aware of any problems that could arise from having the OS
and SQL server on seperate drives? Thanks a lot!No issues that I know of. In fact, having more drives to spread out the I/O
is strongly encouraged.
--Brian
(Please reply to the newsgroups only.)
"Mark" <anonymous@.discussions.microsoft.com> wrote in message
news:398b01c4014b$1477d870$a601280a@.phx.gbl...
> We have a server with one IDE drive which is where the OS
> in located. We have recently purchased a SCSI drive and
> intend on installing SQL Server 2000 on it. Is anyone
> aware of any problems that could arise from having the OS
> and SQL server on seperate drives? Thanks a lot!|||Hi Mark.
There's no problem with separating the drives that the o/s & SQL Server are
on, but you should be aware that by far the most important components to
separate onto different physical disks are SQL Server's .mdf & .ldf files.
There are significant performance and recoverability issues that stem from
this separation and it's the thing that most inexperienced people get wrong.
Regards,
Greg Linwood
SQL Server MVP
"Mark" <anonymous@.discussions.microsoft.com> wrote in message
news:398b01c4014b$1477d870$a601280a@.phx.gbl...
> We have a server with one IDE drive which is where the OS
> in located. We have recently purchased a SCSI drive and
> intend on installing SQL Server 2000 on it. Is anyone
> aware of any problems that could arise from having the OS
> and SQL server on seperate drives? Thanks a lot!

OS and SQL Server installed on seperate drives.

We have a server with one IDE drive which is where the OS
in located. We have recently purchased a SCSI drive and
intend on installing SQL Server 2000 on it. Is anyone
aware of any problems that could arise from having the OS
and SQL server on seperate drives? Thanks a lot!No issues that I know of. In fact, having more drives to spread out the I/O
is strongly encouraged.
--
--Brian
(Please reply to the newsgroups only.)
"Mark" <anonymous@.discussions.microsoft.com> wrote in message
news:398b01c4014b$1477d870$a601280a@.phx.gbl...
> We have a server with one IDE drive which is where the OS
> in located. We have recently purchased a SCSI drive and
> intend on installing SQL Server 2000 on it. Is anyone
> aware of any problems that could arise from having the OS
> and SQL server on seperate drives? Thanks a lot!|||Hi Mark.
There's no problem with separating the drives that the o/s & SQL Server are
on, but you should be aware that by far the most important components to
separate onto different physical disks are SQL Server's .mdf & .ldf files.
There are significant performance and recoverability issues that stem from
this separation and it's the thing that most inexperienced people get wrong.
Regards,
Greg Linwood
SQL Server MVP
"Mark" <anonymous@.discussions.microsoft.com> wrote in message
news:398b01c4014b$1477d870$a601280a@.phx.gbl...
> We have a server with one IDE drive which is where the OS
> in located. We have recently purchased a SCSI drive and
> intend on installing SQL Server 2000 on it. Is anyone
> aware of any problems that could arise from having the OS
> and SQL server on seperate drives? Thanks a lot!