July 3, 2002 at 7:13 am
I am creating clustered indexes on several large tables on different servers.
My pc has grinded to a halt. I was suprised there was an sql client side processing. Who knows what does and doesn't include SOME client side processing??? I know DTS'ing a table goes thru my pc.
-Kevin
July 3, 2002 at 7:43 am
I think DTS is the exception - everything else should run on the server. EM does tend to "hang up" on some of these operations, I think only because its waiting on the command to complete. I usually just run another instance of EM and continue.
Andy
July 3, 2002 at 9:59 am
Tend to agree. you can connect with another instance or QA and run sp_who2 a few times and check that your other connection is still processing.
Steve Jones
July 3, 2002 at 11:30 am
I am still suspicious of what it is doing on my side.
One of my fellow dba's thinks the sql engine behaves differently when you use the gui in comparison to the query analyzer.
Example:
When I drop a populated column on a table ent. manager creates a whole other table and then drops the original.
Does it due this if you use command line?
-KEvin
July 3, 2002 at 11:50 am
It's not the SQL Engine which is behaving differently, it's the way Enterprise Manager is performing actions. Best way to test is to start up Profiler. Run the test using Enterprise Manager. Then run the test using Query Analyzer. In general, Enterprise Manager is going to do a lot more than just a simple statement. It's the price you pay for convenience.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
July 3, 2002 at 12:43 pm
I think some of that is left over from the 6.5 days. You can just issue an alter and the rest will happen, EM scripts out all the stuff the alter would do anyway.
Andy
July 3, 2002 at 2:49 pm
I am always suspect of "I think it works differently"
EM may script different than what you would do, but that does not mean you are doing it wrong.
If you have some evidence of something working differently, I'd love to see it.
Steve Jones
July 3, 2002 at 5:52 pm
Agreed.
EM is going to throw a larger net around things than we would to catch all possibilities since it has to. If we were to write it ourselves, we tend to have all the information we need to make the queries as efficiently as possible. For instance, if we know a user exists in one database and we're seeking to drop the login from SQL Server, we'll only have to check against the one database. EM can't make that assumption and so it'll check 'em all.
But it's not going to cause the engine to work any differently simply because the commands came from EM.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply