| Author |
Topic |
|
Bounty Bob
Starting Member
12 Posts |
 Posted - 2004-04-01 : 04:26:26
|
| Hey Guys,This problem has been bugging me for years, and now, finally, it's wound me up enough that I have to put finger to keyboard and ask if there's a way to turn it off.The problem is that if I leave a results pane open for more than a millisecond I get a message displayed saying there's been no activity for a while and asking if I want to continue using the results. OK, so maybe results panes are memory intensive, but I don't give a monkey's, I've got a gig of memory and just want to be able to work in peace without having to click Yes every 10 seconds.OK, rant over. Anyone know if this is possible? Cheers in advance,Rob |
|
|
samsekar
Constraint Violating Yak Guru
437 Posts |
Posted - 2004-04-01 : 04:35:11
|
| Are you using EM for Selection of records ??, Always use Query Analyser.It is not adivsable to use Enterprise Manager for this type of transactions.- Sekar |
 |
|
|
Bounty Bob
Starting Member
12 Posts |
Posted - 2004-04-01 : 04:57:43
|
| Yep, I'm using Enterprise Manager. I use it really for the ease - it's a lot quicker to right-click a table and select "Return all Rows" than it is to type in the equivalent SELECT query.So why is it not advisable to use Enterprise Manager to return table data? The fact that it contains such useful tools for viewing tables and editing queries/Stored Procedures would seem to imply that this sort of thing is precisely what it's for.Cheers,Rob |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2004-04-01 : 08:37:31
|
quote:
So why is it not advisable to use Enterprise Manager to return table data?
Ummmm, the fact that you're getting an annoying message saying that there's been no activity and the results will be cleared?Seriously, data manipulation is far from ideal in EM. And there are a ton of other problems with it, some subtle, some not. Query Analyzer is a lot better. The SQL Server 2000 version even has an object browser and can generate SQL statements to select rows just as easily as EM can. And while it may take a while to get handy with SQL, you cannot beat the flexibility of hand-written SQL. Things like UNION, CASE expressions, and subqueries can't be done with EM at all. |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-04-01 : 09:00:17
|
| For one thing e-m has problems with some datatypes.Not so much a problem with displaying data but I would strongly advise against using it to update.Another problem is that you can acidentally update easily.As for using it to update SPs etc.It doesn't give an audit trail or history and also just displays what is in syscomments and may not refer to the actual object that is being updated.From a remote connection it can be very (very, very) slow.You will find it's deficiencies if you carry on using it and eventually do everything in query analyser.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
Bounty Bob
Starting Member
12 Posts |
Posted - 2004-04-01 : 10:47:21
|
| Wow, I had no idea that EM was so universally reviled. I assume you all still use it to create tables since writing out 30+ CREATE TABLE's would take far too long. There are a few other things that niggle me about EM, like it's insistence in reformatting my SQL when I modify a view. Also since I've found out how to change the font in QA I'm more likely to use it. One of my gripes about QA was that I could only realistically view data on the screen from 2 tables at a time whereas in EM I could view up to half a dozen (sometimes necessary, sometimes overkill). |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-04-01 : 10:56:41
|
| Actually, most of us have used QA for so long, we can do it easier in QA. Cut and paste is a wonderful tool.Look at the scripts that EM uses when you create tables that have foreign keys to existing tables. Also look at what it does when you modify tables. After you pick yourself off the floor in shock, you'll use QA happily.If you learn how to use it and build up a good script library, you'll never regret it. You have much more control. You'll learn to do things just as fast. And, you'll really know how it's all working because you wrote it.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-04-01 : 11:02:08
|
| >> I assume you all still use it to create tables since writing out 30+ CREATE TABLE's would take far too long. Nope.see http://www.nigelrivett.net/SQLServerReleaseControl.htmhttp://www.nigelrivett.net/sqlserverdevelopment.html==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
Bounty Bob
Starting Member
12 Posts |
Posted - 2004-04-01 : 11:43:12
|
| Yeah, EM generated scripts are a nightmare. That's where we get our audit trail from, ie. make a change, script it, bang it into sourcesafe. I'll have a look at the links tonight, cheers for that. |
|
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2004-04-01 : 12:10:59
|
quote:
Originally posted by Bounty Bob
One of my gripes about QA was that I could only realistically view data on the screen from 2 tables at a time whereas in EM I could view up to half a dozen (sometimes necessary, sometimes overkill).
I don't see how EM does this better/faster/easier than QA. My guess is that you're only using one window in QA. I run multiple windows if I'm dealing with multiple queries, and my query results stay in their proper window. And using CTRL-TAB I can switch between windows quickly.In fact, using multiple windows can be really handy to do a BEFORE-AFTER comparison of an UPDATE statement (preferably within an uncommitted transaction in case you need to rollback).--------------------------------------------------------------Find more words of wisdom at [url]http://weblogs.sqlteam.com/markc[/url] |
|
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2004-04-01 : 20:17:42
|
I create all my tables in script, I use a Codesmith [1](yes, another plug  ) template to generate the stub with a couple of standard fields I use. I also have another template that given two table names and their key names will create a many-many join table script.I find this so much faster than enterprise manager.[1] http://www.ericjsmith.net/codesmith/Damian |
|
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2004-04-01 : 23:12:49
|
| Careful Damian, you're liable to get labeled the Codesmith Pimp. I hope you're getting paid at least as well as Rob Volk did for being the Guru's Guide to Transact-SQL by Ken Henderson Pimp.--------------------------------------------------------------Find more words of wisdom at [url]http://weblogs.sqlteam.com/markc[/url] |
|
|
|
Bounty Bob
Starting Member
12 Posts |
Posted - 2004-04-02 : 04:21:47
|
| Hi AjarnMark. I was using multiple windows in QA but since the font size defaulted to 10pt Courier, and at the time I didn't realise you could change the font :o , I couldn't physically fit more than a couple of windows on the monitor ... well, I suppose I could have done but I would have had to sacrifice being able to view the query and any more than half a dozen rows of data in each.Getting more convinced by the QA argument now. Especially after discovering that you can do more than merely write queries and run them. |
|
|
|
|
Really annoying SQL Server feature