[dba-SQLServer] What is going on

JWColby jwcolby at colbyconsulting.com
Wed Nov 1 21:37:38 CST 2006


Jim,

No, I actually appreciate the lecture if it works.  I don't have an issue
with going there if I am capable.  I tried it on my past mb and it wouldn't
install for the simple reason that the driver disk did a check and refused
to install because it wasn't XP.  This MB does not have that problem.  All I
have to do now is wait for SQL Server to stop.  I could reboot the machine
but that would just cause more problems down the road I am sure.  I have to
detach this database before I start the OS install.

Tomorrow sounds like fun.  8-(

John W. Colby
Colby Consulting
www.ColbyConsulting.com

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim
Lawrence
Sent: Wednesday, November 01, 2006 10:12 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] What is going on

Hi John:

As you are not going, right at the start, into Active Directory (workgroups
will work fine), installing Server2003 is as simple as installing XP.. The
whole process tends to be a disk jockey nodding off between switch disk and
answering such questions as, "What is your product key" and do you want to
install IIS. If I can do it so can you.

Server2003 can run multiple instances and processes. It will run
applications that will over-load any XP desktop box. It has better isolation
so if a program misbehaves it does not bring down the system. I understood
you were on the MS partner plan and therefore you should have access to all
the servers you can stand. Server 2003 standard or developer is just fine
unless you are planning to run virtual and exchange server etc.

I have taken the luxury to run Server 2003 as my desktop, one that has never
gone down... Well only once and that was my fault... But it is really
stable. MS SQL and IIS run as background processes and their impact is
hardly noticeable. 

Sorry if this sounds like a lecture but I am sure your problems can be
solved by going this route.    

Jim

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby
Sent: Wednesday, November 01, 2006 2:52 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] What is going on

LOL, borderline insanity.  I can assure you that I am FULLY insane.  Bwaaa
haaaa haaaa.  I am using SP Pro.  SQL Server ran just fine on 2K pro, XP Pro
is the 2K Pro base code.  Why would it not run on that?  I keep hearing that
it isn't supposed to, but it does.  I can tell you I would be irritated
beyond belief if I went to Win 2003 server (which I have but haven't a clue
how to install, since this is a desktop machine in the end) and I still had
this issue.

I actually tried to install 2003 server (in fact I have a disk with the
beginnings of the install) and got to questions that implied I was supposed
to know what I was doing (and I don't) so how am I supposed to install 2003
so that I can test your theory?

I am not a notwork / OS admin, I am a developer.  MS themselves push SQL
Server lite as a developer tool.  

If anyone wants to talk me through a 2003 server install I will do that
but...

John W. Colby
Colby Consulting
www.ColbyConsulting.com

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim
Lawrence
Sent: Wednesday, November 01, 2006 5:19 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] What is going on

Hi John:

I am trying to cover all the bases. The problems initially appears to be
with the MS SQL sever setting as they run fairly indendendantly from an OS.
If the problem is not in the MS SQL setup, accumulating non responsive
results sort of negates the hardware being the issue, then it has to be in
the process. 

If it is absolutely not in the process then it must be in the MS SQL
settings.

Please tell me you are using server OS as it would be border-line insanity
to use a desktop type OS and then I would assure you, without hesitation,
that that is the problem.

HTH
Jim    

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of JWColby
Sent: Wednesday, November 01, 2006 12:12 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] What is going on

Jim,

I don't understand what this is doing for me.  I have just one data file
ATM.  I don't know whether that is a good thing or a bad thing.  This sounds
like the process for creating and then redistributing data amongst multiple
files.  If you are saying that it is the existence of one huge file that is
causing my slowdown, then I can certainly do that.  



I have to ask if this is as good as it gets with SQL Server.  I understand
that I am doing stuff with big tables but keerimeny.  I started the build of
a PKID field on the big table.  It tells me that "ansi nulls was not on and
it has to rebuild the table" so I do.  EM just locks up tight, won't even
redraw the screen (blank white) if you switch away and back again.  I
believe that it is hard at work but folks, this is the age of threads.

So I open another instance of EM to work with another table.  EM takes
several seconds to expand each tree (server, databases, specific database)
then when I try to expand the tables, the second instance of EM locks up
tight with an hourglass.  I mean c'mon.  This is 2006, a monster (desktop)
system and EM acts as if it is a DOS app from 1986 running on a '286 with 4
megs and swapping memory.  The second EM instance has been trying to open
the tables icon just to show me what tables are there for 20 minutes now.

To say this is discouraging to work with would be an understatement.  If
this is the best I am going to get I am going to have to look for another
database engine to work with.

And the most discouraging part is that my dual proc system is cruising along
using (average?) well under 25% of the processor while EM is locked up
tight.

Does SQl Server 2005 fix any of this?  Or should I just go look at MySQL or
Oracle personal edition.  I have to get work done on this database and it is
telling me that one job (building a field / index) on one table is all it
can handle.  And by the looks of it I will be locked out of this database
for the next 12 to 24 hours.  

Hell, ACCESS can do better than this!!!  Well, maybe not but SQL Server's
rep is taking a beating here.

John W. Colby
Colby Consulting
www.ColbyConsulting.com

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com




More information about the dba-SQLServer mailing list