Showing posts with label company. Show all posts
Showing posts with label company. Show all posts

Friday, March 30, 2012

Help in choosing SQL Server edition

My company has a website that connects to a sql server (on a different box). I am trying to convince them to get sql server 2005. However, I do not know if SQL Server 2005 Workgroup edition is okay for our needs. Can someone please tell me if it is.

Basically, our setup is the following:

The SQL Server will only have one/two clients - the web server

The SQL Server will have a number of different user accounts though

The SQL Server will have its databases replicated to another SQL Server - both will be 2005

The SQL Server will not have more than 4Gb of RAM

The SQL Server will only have one processor - possible Xeon, and/or Dual Core

The database will not have complicated analysis done on them. The most that will be done are complicated selects which indexing should be able to handle.

We use crystal reports.

Thank you for any help.

Jagdip.

One other big consideration to make in your analysis is the volume of traffic you're going to have to the web server. If your web server is incredibly active and is going to be hammering the SQL server with requests, that will definitely affect your decision.

This page illustrates the differences between the editions:

http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx

Off the bat, it sounds like one feature that the Workgroup edition might lack that you need is Mirroring. Other than that, from what you described, I would think that the Workgroup edition would be fine for you. If you can find a way around the requirement for Mirroring (some other replication scheme--several exist), then you might be able to stick with the Workgroup rather than going with Standard.

Ryan

|||

Hi ya,

You have got a difficult choice. Well if you don't want to have that much and can replicate using your own logic then Sql Server express, the only limit for Database size which is a 4 GB. Workgroup would be better but you have got RAM limit of 3 GB although no limit on actual DB itself.

If you want to be cost effective then use SQL Express, if you can okay with small cost then workgroup

You can read the whole comparision about it from thislink

Hope that helps

Cheers

|||

Thank you both for your replies.

SQL Express is not an option as some of the databases are already over 4Gb.

The volume of traffic is not going to be great. If things go the way they are, we are looking at about 10 users per hour !!!

Thank you for the links as well. I had read these and was still unsure. Database Mirroring sounds good - but we are implementing a failover solution on the web server instead. If the primary web server/database fails over, then the secondaries will become active (using either Neverfail or Doubletake software). We are planning on using merge replication, so this should not be a problem.

The one thing I am worried about is the number of clients that can access the sql server simultaneously. Will the sql server restrict the number of users logged at once?

|||

I can't find anything anywhere about a limit on concurrent users for Workgroup Edition. If any of you SQL guys out there know of one, please chime in. It sounds like you're looking at VERY low usage though, so you should be fine. Were it not for your other requirements, SQL Express would be the perfect solution here. It sounds like you have a good plan in place and like you've got a good idea of which product is the right one for you. The nice thing about SQL is that it's easy to upgrade down the road as well, so if your requirements change in the future you should remain flexible.

|||

Hi ya,

If sql express is out of the question still workgroup would be more then enough as there is no hard core limit on concurrent no of users that can attach to a Sql Server. However it does depend on the actual machine performance which you already explained would be having 2-3 GB.

Hope that helps

Cheers

|||

Brilliant.

I just found out that we do not need to spend £300 for a server license of visual sourcesafe - so the money will hopefully go towards a new sql server.

|||Awesome. That worked out great. I'm glad you were able to find the right product for your needs.

Wednesday, March 28, 2012

Help gathering SQL info from all servers - noobie alert :)

I'm a domain admin, not a SQL guy. Unfortunately I have been tasked with
finding all SQL servers in the company and coming up with a migration plan
to a single SQL cluster.
The issue at hand is that I'm hoping not to try to reinvent the wheel... is
there any script (vb, js, osql, something), that will query a list of known
SQL servers and output the database names and sizes to a text/csv file?
If it could go one step further and give me other info like usernames and
such that would be great too!
Thanks for any help you can give!
Aaron
Do a scan for anything listening on port 1433 and you should find all of
your SQL Servers. You will have to factor out anything that is nothing more
than local MSDE due to some application install.
Once you have the server names, you can connect to them with a trusted
connection (proxies your domain admin authority). The list of databases can
be found by using "select * from master.dbo.sysdatabases". The list of
users can be found by using "select * from master.dbo.sysxlogins".
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"livin" <livin@.@.cox.net> wrote in message
news:rDxuf.676$B93.22@.fed1read07...
> I'm a domain admin, not a SQL guy. Unfortunately I have been tasked with
> finding all SQL servers in the company and coming up with a migration plan
> to a single SQL cluster.
> The issue at hand is that I'm hoping not to try to reinvent the wheel...
> is there any script (vb, js, osql, something), that will query a list of
> known SQL servers and output the database names and sizes to a text/csv
> file?
> If it could go one step further and give me other info like usernames and
> such that would be great too!
> Thanks for any help you can give!
> Aaron
>
>
|||Hi
Look at SQLRecon on http://www.sqlsecurity.com/DesktopDe...aspx?tabid=26,
you will need the rights to access these servers to audit the database
details you may want to look at
http://www.sqlservercentral.com/scri...?scriptid=1589
John
"livin" <livin@.@.cox.net> wrote in message
news:rDxuf.676$B93.22@.fed1read07...
> I'm a domain admin, not a SQL guy. Unfortunately I have been tasked with
> finding all SQL servers in the company and coming up with a migration plan
> to a single SQL cluster.
> The issue at hand is that I'm hoping not to try to reinvent the wheel...
> is there any script (vb, js, osql, something), that will query a list of
> known SQL servers and output the database names and sizes to a text/csv
> file?
> If it could go one step further and give me other info like usernames and
> such that would be great too!
> Thanks for any help you can give!
> Aaron
>
>
|||Hi living,
just for fun I wrote a Application for you to gather this information
for all servers / all databases which put this information into an XML
file which can be easily used in Excel or some other program. If you
(or any other guy) is Interested in just drop me a mail, i=B4ll send it
to you, later on after finishing the building of my new portal
www.sqlserver2005.de I will put it up there. It uses the new SQL.SMO
and the .net 2.0 to collect this information.
HTH, Jens Suessmeyer.
|||You guys rock!
Thanks for helping out a noobie... I DL'd all the stuff and will have fun
with it this week!
Jens... sending you an email now.
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1136325248.839414.309600@.g49g2000cwa.googlegr oups.com...
Hi living,
just for fun I wrote a Application for you to gather this information
for all servers / all databases which put this information into an XML
file which can be easily used in Excel or some other program. If you
(or any other guy) is Interested in just drop me a mail, ill send it
to you, later on after finishing the building of my new portal
www.sqlserver2005.de I will put it up there. It uses the new SQL.SMO
and the .net 2.0 to collect this information.
HTH, Jens Suessmeyer.

Friday, March 9, 2012

HELP - SRS for Developer Ed installed instead of for Standard Ed.

I have been getting ready to finally put into my company's Production
Environment all the reports I have been developing in our Test Environment.
The Test Environment is SQL 2000 Developer Edition, and SRS was installed via
the CD that came in the box - I read that it said "For SQL Server 2000
Developer Edition only."
The decision was made that we did not need Enterprise Edition features, so a
Standard Edition SQL Server 2000 license was purchased and installed, be my
supervisor. He then used the SAME CD for SRS to install that I did. His
logic was "These Microsoft disks can detect what version of SQL Server is
running, and only install the components for the version detected."
I was unaware of this and have been loading the new server with reports and
running the Report Snapshots for the LONG RUNNING REPORTS, and setting up the
Shared Schedules and Permissions for the 125+ reports. I was about to start
creating the Manual Subscriptions for the various reports when I noticed the
'New Data-driven Subscription' button, and then realized what happened.
I would like to avoid redoing work, if possible. Is there a way to
over-install the Standard Edition Version of SQL Reporting Services on top of
the Developer Edition, so I don't have to re-setup everything? Is there a
way to downgrade/upgrade Editions without having to re-build the site?It is possible to do this. Before starting anything, of course, backup your
databases and the report server encryption key (see help topics on backing
up report server).
1. Uninstall the developer edition (this will not remove the report server
databases)
2. Install the standard edition. When asked for a database, use a new one.
Do NOT use the one from the developer install
3. After installation is complete, run rsconfig to point the new
installation at the old database
4. Delete the temporary database that you created as part of step 2.
If you created any data driven subscriptions, they will no longer run with
standard installed.
--
This posting is provided "AS IS" with no warranties, and confers no rights
"Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> I have been getting ready to finally put into my company's Production
> Environment all the reports I have been developing in our Test
Environment.
> The Test Environment is SQL 2000 Developer Edition, and SRS was installed
via
> the CD that came in the box - I read that it said "For SQL Server 2000
> Developer Edition only."
> The decision was made that we did not need Enterprise Edition features, so
a
> Standard Edition SQL Server 2000 license was purchased and installed, be
my
> supervisor. He then used the SAME CD for SRS to install that I did. His
> logic was "These Microsoft disks can detect what version of SQL Server is
> running, and only install the components for the version detected."
> I was unaware of this and have been loading the new server with reports
and
> running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
the
> Shared Schedules and Permissions for the 125+ reports. I was about to
start
> creating the Manual Subscriptions for the various reports when I noticed
the
> 'New Data-driven Subscription' button, and then realized what happened.
> I would like to avoid redoing work, if possible. Is there a way to
> over-install the Standard Edition Version of SQL Reporting Services on top
of
> the Developer Edition, so I don't have to re-setup everything? Is there a
> way to downgrade/upgrade Editions without having to re-build the site?|||I followed your instructions, except I hadn't yet deleted the 'temp' database
yet - didn't want to get rid of it until I knew things are working. They
aren't. I get the following error now:
This edition of Reporting Services does not support web farm deployment.
(rsInvalidRSEditionConfiguration) Get Online Help
Online help says the following:
You cannot use the Standard edition of Reporting Services to deploy multiple
report servers in a Web farms.
I am not using a Web Farm. I have one server that houses the source
databases for my company, and this SRS server that hosts the IIS website and
the SRS databases, both with standard edition. The RDS file points to the
source database server. Is this what SRS consideres a Web Farm? According
to your schemeatics on Reporting Services I have a proper license for both
servers.
"Brian Hartman [MSFT]" wrote:
> It is possible to do this. Before starting anything, of course, backup your
> databases and the report server encryption key (see help topics on backing
> up report server).
> 1. Uninstall the developer edition (this will not remove the report server
> databases)
> 2. Install the standard edition. When asked for a database, use a new one.
> Do NOT use the one from the developer install
> 3. After installation is complete, run rsconfig to point the new
> installation at the old database
> 4. Delete the temporary database that you created as part of step 2.
> If you created any data driven subscriptions, they will no longer run with
> standard installed.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
> "Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
> message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> > I have been getting ready to finally put into my company's Production
> > Environment all the reports I have been developing in our Test
> Environment.
> > The Test Environment is SQL 2000 Developer Edition, and SRS was installed
> via
> > the CD that came in the box - I read that it said "For SQL Server 2000
> > Developer Edition only."
> >
> > The decision was made that we did not need Enterprise Edition features, so
> a
> > Standard Edition SQL Server 2000 license was purchased and installed, be
> my
> > supervisor. He then used the SAME CD for SRS to install that I did. His
> > logic was "These Microsoft disks can detect what version of SQL Server is
> > running, and only install the components for the version detected."
> >
> > I was unaware of this and have been loading the new server with reports
> and
> > running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
> the
> > Shared Schedules and Permissions for the 125+ reports. I was about to
> start
> > creating the Manual Subscriptions for the various reports when I noticed
> the
> > 'New Data-driven Subscription' button, and then realized what happened.
> >
> > I would like to avoid redoing work, if possible. Is there a way to
> > over-install the Standard Edition Version of SQL Reporting Services on top
> of
> > the Developer Edition, so I don't have to re-setup everything? Is there a
> > way to downgrade/upgrade Editions without having to re-build the site?
>
>|||I went ahead and deleted the new 'temp' databases after running rsconfig
again. I still get the same errors listed below.
"Rob 'Spike' Stevens" wrote:
> I followed your instructions, except I hadn't yet deleted the 'temp' database
> yet - didn't want to get rid of it until I knew things are working. They
> aren't. I get the following error now:
> This edition of Reporting Services does not support web farm deployment.
> (rsInvalidRSEditionConfiguration) Get Online Help
> Online help says the following:
> You cannot use the Standard edition of Reporting Services to deploy multiple
> report servers in a Web farms.
> I am not using a Web Farm. I have one server that houses the source
> databases for my company, and this SRS server that hosts the IIS website and
> the SRS databases, both with standard edition. The RDS file points to the
> source database server. Is this what SRS consideres a Web Farm? According
> to your schemeatics on Reporting Services I have a proper license for both
> servers.
> "Brian Hartman [MSFT]" wrote:
> > It is possible to do this. Before starting anything, of course, backup your
> > databases and the report server encryption key (see help topics on backing
> > up report server).
> >
> > 1. Uninstall the developer edition (this will not remove the report server
> > databases)
> > 2. Install the standard edition. When asked for a database, use a new one.
> > Do NOT use the one from the developer install
> > 3. After installation is complete, run rsconfig to point the new
> > installation at the old database
> > 4. Delete the temporary database that you created as part of step 2.
> >
> > If you created any data driven subscriptions, they will no longer run with
> > standard installed.
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights
> >
> > "Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
> > message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> > > I have been getting ready to finally put into my company's Production
> > > Environment all the reports I have been developing in our Test
> > Environment.
> > > The Test Environment is SQL 2000 Developer Edition, and SRS was installed
> > via
> > > the CD that came in the box - I read that it said "For SQL Server 2000
> > > Developer Edition only."
> > >
> > > The decision was made that we did not need Enterprise Edition features, so
> > a
> > > Standard Edition SQL Server 2000 license was purchased and installed, be
> > my
> > > supervisor. He then used the SAME CD for SRS to install that I did. His
> > > logic was "These Microsoft disks can detect what version of SQL Server is
> > > running, and only install the components for the version detected."
> > >
> > > I was unaware of this and have been loading the new server with reports
> > and
> > > running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
> > the
> > > Shared Schedules and Permissions for the 125+ reports. I was about to
> > start
> > > creating the Manual Subscriptions for the various reports when I noticed
> > the
> > > 'New Data-driven Subscription' button, and then realized what happened.
> > >
> > > I would like to avoid redoing work, if possible. Is there a way to
> > > over-install the Standard Edition Version of SQL Reporting Services on top
> > of
> > > the Developer Edition, so I don't have to re-setup everything? Is there a
> > > way to downgrade/upgrade Editions without having to re-build the site?
> >
> >
> >|||Also, Iâ'm finding this error message in the application log:
Reporting Services components from different editions cannot be used together.
"Rob 'Spike' Stevens" wrote:
> I went ahead and deleted the new 'temp' databases after running rsconfig
> again. I still get the same errors listed below.
> "Rob 'Spike' Stevens" wrote:
> > I followed your instructions, except I hadn't yet deleted the 'temp' database
> > yet - didn't want to get rid of it until I knew things are working. They
> > aren't. I get the following error now:
> >
> > This edition of Reporting Services does not support web farm deployment.
> > (rsInvalidRSEditionConfiguration) Get Online Help
> >
> > Online help says the following:
> > You cannot use the Standard edition of Reporting Services to deploy multiple
> > report servers in a Web farms.
> >
> > I am not using a Web Farm. I have one server that houses the source
> > databases for my company, and this SRS server that hosts the IIS website and
> > the SRS databases, both with standard edition. The RDS file points to the
> > source database server. Is this what SRS consideres a Web Farm? According
> > to your schemeatics on Reporting Services I have a proper license for both
> > servers.
> >
> > "Brian Hartman [MSFT]" wrote:
> >
> > > It is possible to do this. Before starting anything, of course, backup your
> > > databases and the report server encryption key (see help topics on backing
> > > up report server).
> > >
> > > 1. Uninstall the developer edition (this will not remove the report server
> > > databases)
> > > 2. Install the standard edition. When asked for a database, use a new one.
> > > Do NOT use the one from the developer install
> > > 3. After installation is complete, run rsconfig to point the new
> > > installation at the old database
> > > 4. Delete the temporary database that you created as part of step 2.
> > >
> > > If you created any data driven subscriptions, they will no longer run with
> > > standard installed.
> > >
> > > --
> > > This posting is provided "AS IS" with no warranties, and confers no rights
> > >
> > > "Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
> > > message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> > > > I have been getting ready to finally put into my company's Production
> > > > Environment all the reports I have been developing in our Test
> > > Environment.
> > > > The Test Environment is SQL 2000 Developer Edition, and SRS was installed
> > > via
> > > > the CD that came in the box - I read that it said "For SQL Server 2000
> > > > Developer Edition only."
> > > >
> > > > The decision was made that we did not need Enterprise Edition features, so
> > > a
> > > > Standard Edition SQL Server 2000 license was purchased and installed, be
> > > my
> > > > supervisor. He then used the SAME CD for SRS to install that I did. His
> > > > logic was "These Microsoft disks can detect what version of SQL Server is
> > > > running, and only install the components for the version detected."
> > > >
> > > > I was unaware of this and have been loading the new server with reports
> > > and
> > > > running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
> > > the
> > > > Shared Schedules and Permissions for the 125+ reports. I was about to
> > > start
> > > > creating the Manual Subscriptions for the various reports when I noticed
> > > the
> > > > 'New Data-driven Subscription' button, and then realized what happened.
> > > >
> > > > I would like to avoid redoing work, if possible. Is there a way to
> > > > over-install the Standard Edition Version of SQL Reporting Services on top
> > > of
> > > > the Developer Edition, so I don't have to re-setup everything? Is there a
> > > > way to downgrade/upgrade Editions without having to re-build the site?
> > >
> > >
> > >|||I was able to find a solution. Thanks for the help you did provide.
"Rob 'Spike' Stevens" wrote:
> Also, Iâ'm finding this error message in the application log:
> Reporting Services components from different editions cannot be used together.
>
> "Rob 'Spike' Stevens" wrote:
> > I went ahead and deleted the new 'temp' databases after running rsconfig
> > again. I still get the same errors listed below.
> >
> > "Rob 'Spike' Stevens" wrote:
> >
> > > I followed your instructions, except I hadn't yet deleted the 'temp' database
> > > yet - didn't want to get rid of it until I knew things are working. They
> > > aren't. I get the following error now:
> > >
> > > This edition of Reporting Services does not support web farm deployment.
> > > (rsInvalidRSEditionConfiguration) Get Online Help
> > >
> > > Online help says the following:
> > > You cannot use the Standard edition of Reporting Services to deploy multiple
> > > report servers in a Web farms.
> > >
> > > I am not using a Web Farm. I have one server that houses the source
> > > databases for my company, and this SRS server that hosts the IIS website and
> > > the SRS databases, both with standard edition. The RDS file points to the
> > > source database server. Is this what SRS consideres a Web Farm? According
> > > to your schemeatics on Reporting Services I have a proper license for both
> > > servers.
> > >
> > > "Brian Hartman [MSFT]" wrote:
> > >
> > > > It is possible to do this. Before starting anything, of course, backup your
> > > > databases and the report server encryption key (see help topics on backing
> > > > up report server).
> > > >
> > > > 1. Uninstall the developer edition (this will not remove the report server
> > > > databases)
> > > > 2. Install the standard edition. When asked for a database, use a new one.
> > > > Do NOT use the one from the developer install
> > > > 3. After installation is complete, run rsconfig to point the new
> > > > installation at the old database
> > > > 4. Delete the temporary database that you created as part of step 2.
> > > >
> > > > If you created any data driven subscriptions, they will no longer run with
> > > > standard installed.
> > > >
> > > > --
> > > > This posting is provided "AS IS" with no warranties, and confers no rights
> > > >
> > > > "Rob 'Spike' Stevens" <RobSpikeStevens@.discussions.microsoft.com> wrote in
> > > > message news:060F4BF0-885C-45A6-A871-3BBC19EF6617@.microsoft.com...
> > > > > I have been getting ready to finally put into my company's Production
> > > > > Environment all the reports I have been developing in our Test
> > > > Environment.
> > > > > The Test Environment is SQL 2000 Developer Edition, and SRS was installed
> > > > via
> > > > > the CD that came in the box - I read that it said "For SQL Server 2000
> > > > > Developer Edition only."
> > > > >
> > > > > The decision was made that we did not need Enterprise Edition features, so
> > > > a
> > > > > Standard Edition SQL Server 2000 license was purchased and installed, be
> > > > my
> > > > > supervisor. He then used the SAME CD for SRS to install that I did. His
> > > > > logic was "These Microsoft disks can detect what version of SQL Server is
> > > > > running, and only install the components for the version detected."
> > > > >
> > > > > I was unaware of this and have been loading the new server with reports
> > > > and
> > > > > running the Report Snapshots for the LONG RUNNING REPORTS, and setting up
> > > > the
> > > > > Shared Schedules and Permissions for the 125+ reports. I was about to
> > > > start
> > > > > creating the Manual Subscriptions for the various reports when I noticed
> > > > the
> > > > > 'New Data-driven Subscription' button, and then realized what happened.
> > > > >
> > > > > I would like to avoid redoing work, if possible. Is there a way to
> > > > > over-install the Standard Edition Version of SQL Reporting Services on top
> > > > of
> > > > > the Developer Edition, so I don't have to re-setup everything? Is there a
> > > > > way to downgrade/upgrade Editions without having to re-build the site?
> > > >
> > > >
> > > >

Friday, February 24, 2012

HELP

I have been looking at several programs for an auction company . I used my f
irewall and virus check before trying any demo's . Some are OK some not suit
able. One uses and loaded SQL and ? on my computer and it has never been th
e same since. Any ideas ? T
he program adm has tried hard to help me out but at this point I would like
to uninstall it Can Not
because SQL and ? never fully installed . Would like to restore my sys (and
learn more about SQL) without going thru a XP sys restore.(it did not work f
or awhile after the program install and took 2 days to fix ) I love knowing
how my computer works(start
ed with 8088)But time to let experts help. Wish I could keep up with the cha
nge as fast it happens today.Last things first.
If you want to understand SQL better, a good free place to start is Books
On-Lon (BOL for short), included free or available for download here:
SQL Server 2000 Books Online (Updated - SP3)
http://www.microsoft.com/downloads/...71A6-BCF4-45A6-
A2E2-F6AB5BE3EF12&displaylang=en
Another good general resource on SQL server is Inside SQL 2000 by Kalen
Delaney, but you will have to pay for that. She has to earn a living
somehow.
Now for the really important part. Here is how to remove a broken SQL
install:. I hope you are comfortable with registry changes, because that is
the only way to deal with a broken install of any app. It is not simple,
but it is a better alternative than a total system rebuild.
HOW TO: Manually Remove SQL Server 2000 Default, Named, or Virtual Instance
http://support.microsoft.com/defaul...1&Product=sql2k
If you have more questions you know where to go.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
CareerBuilder.com
"need2know" <rsjones@.wapda.com> wrote in message
news:057E5FA0-BBEB-410A-A2DC-147B4E1C02F2@.microsoft.com...
quote:

> I have been looking at several programs for an auction company . I used my

firewall and virus check before trying any demo's . Some are OK some not
suitable. One uses and loaded SQL and ? on my computer and it has never
been the same since. Any ideas ? The program adm has tried hard to help me
out but at this point I would like to uninstall it Can Not
quote:

> because SQL and ? never fully installed . Would like to restore my sys

(and learn more about SQL) without going thru a XP sys restore.(it did not
work for awhile after the program install and took 2 days to fix ) I love
knowing how my computer works(started with 8088)But time to let experts
help. Wish I could keep up with the change as fast it happens today.
quote:

>

Sunday, February 19, 2012

HELP

I have been looking at several programs for an auction company . I used my firewall and virus check before trying any demo's . Some are OK some not suitable. One uses and loaded SQL and ? on my computer and it has never been the same since. Any ideas ? The program adm has tried hard to help me out but at this point I would like to uninstall it Can No
because SQL and ? never fully installed . Would like to restore my sys (and learn more about SQL) without going thru a XP sys restore.(it did not work for awhile after the program install and took 2 days to fix ) I love knowing how my computer works(started with 8088)But time to let experts help. Wish I could keep up with the change as fast it happens today.Last things first. :)
If you want to understand SQL better, a good free place to start is Books
On-Lon (BOL for short), included free or available for download here:
SQL Server 2000 Books Online (Updated - SP3)
http://www.microsoft.com/downloads/details.aspx?FamilyID=683D71A6-BCF4-45A6-
A2E2-F6AB5BE3EF12&displaylang=en
Another good general resource on SQL server is Inside SQL 2000 by Kalen
Delaney, but you will have to pay for that. She has to earn a living
somehow.
Now for the really important part. Here is how to remove a broken SQL
install:. I hope you are comfortable with registry changes, because that is
the only way to deal with a broken install of any app. It is not simple,
but it is a better alternative than a total system rebuild.
HOW TO: Manually Remove SQL Server 2000 Default, Named, or Virtual Instance
http://support.microsoft.com/default.aspx?scid=kb;en-us;290991&Product=sql2k
If you have more questions you know where to go.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
CareerBuilder.com
"need2know" <rsjones@.wapda.com> wrote in message
news:057E5FA0-BBEB-410A-A2DC-147B4E1C02F2@.microsoft.com...
> I have been looking at several programs for an auction company . I used my
firewall and virus check before trying any demo's . Some are OK some not
suitable. One uses and loaded SQL and ? on my computer and it has never
been the same since. Any ideas ? The program adm has tried hard to help me
out but at this point I would like to uninstall it Can Not
> because SQL and ? never fully installed . Would like to restore my sys
(and learn more about SQL) without going thru a XP sys restore.(it did not
work for awhile after the program install and took 2 days to fix ) I love
knowing how my computer works(started with 8088)But time to let experts
help. Wish I could keep up with the change as fast it happens today.
>