Suggestions? (Full Version)

All Forums >> [Web Development] >> ASP, PHP, and Database



Message

fhenkel -> Suggestions? (5/2/2006 13:26:24)

I am currently running Server 2003 with SQL2000 as the database portion. I'm currently looking at switching to MySQL and then installing PHP. I'm brand new to PHP and just about every book I've found on PHP seems to recomend using MySQl. What I'm wondering is if I can succesfully uninstall the SQL2000 without it having an adverse effect on my sites which are not using the SQL anyway. All my ASP work is using Access. I installed SQL2000 when I first built the server with the intent of creating some Sharepoint sites but the small businesses I host did not need Sharepoint only Frontpage Extensions. I'd like to start using the PHP with their sites but do not want to crah the server with removing the SQL2000. We all know how well Microsoft does their uninstalls. Any suggestions appreciated?



rdouglass -> RE: Suggestions? (5/2/2006 14:06:45)

quote:

All my ASP work is using Access.


Just turn the SQL Service off for a few days to confirm this before you un-install.

I know of nothing in FrontPage or FP Extensions that would require SQL Server.



fhenkel -> RE: Suggestions? (5/3/2006 16:40:14)

Thanks, I'll try that and see what happens. Would it also be needed to remove the SharePoint Services from the server also, if this works?



Spooky -> RE: Suggestions? (5/3/2006 17:13:24)

Personally Id just leave it there but turn off the service



fhenkel -> RE: Suggestions? (5/4/2006 16:43:32)

spooky, so you don't see any reason for removing the SQL2000 as long as I have the service shut off? I have shut the service down and set it to "manual" and all seems to be working fine with the sites. I was about to install MySQL and the PHP5 on the server. Do you foresee any problem related to the PHP using MySQL even if it finds the SQL2000 still there or is it only looking for what database service is running? Thanks.

I'll hold off installing until I hear back from you on that.



Spooky -> RE: Suggestions? (5/4/2006 19:08:24)

No, shouldnt be a problem at all - many hosts run the same setup.
You dont necessarily have to use php, asp will work well with mySQL too



fhenkel -> RE: Suggestions? (5/5/2006 13:06:31)

Ok, that seems clear but now I have the Dumb question of the day. I'm under the impression that I need to go to learning PHP & MySQL in order to somehow make the sites more interactive. I have already been working with ASP for awhile now building database oriented sites for our car club events around the country. I have built several Online Registration's for the owners to sign up for an event and it displays their info and pulls many Reports for the event organizers. An example is that if an event will be selling "Event Shirts", they can see how many, what sizes, if men's or women's, and the Report also gives them a total of each size and the pricing. All this is handled through ASP and Access. Along those lines would PHP just be replacing the ASP? If so it would sound like I don't need the PHP & MySQL?? Awaiting your input. I guess another question is what does using PHP offer.



dpf -> RE: Suggestions? (5/5/2006 13:37:52)

quote:

Along those lines would PHP just be replacing the ASP? If so it would sound like I don't need the PHP & MySQL?? Awaiting your input. I guess another question is what does using PHP offer.
PHP wont give you anything you dont already have with ASP



fhenkel -> RE: Suggestions? (5/5/2006 15:25:49)

Thanks for the info. Looks like I'll be staying with ASp and Access and then move to using SQL2000 later.



yb2 -> RE: Suggestions? (5/5/2006 15:33:26)

most people use mySQL and PHP because they are free. If you run them on a Windows server then they are still free but you're paying for a Server 2003 license.

Unless you're moving to a Linux server and you are very familiar with mySQL and PHP then stick with what you've got, and use either of the free versions of SQL Server (Express or MSDE).



dpf -> RE: Suggestions? (5/5/2006 16:14:16)

quote:

the free versions of SQL Server (Express or MSDE).
ok help me out here yb, i cant ever get it into my head. define sql server- express and msde and sql2000 - whats the diff? are they all db engines?



yb2 -> RE: Suggestions? (5/5/2006 16:20:36)

they're all db engines, the only difference between the standard and the free (without looking it up) is that the free is limited to 4GB total for a single db, and you don't get replication.

MSDE (free) is the same engine as SQL Server 2000
SQL Server Express (free) is the same engine as SQL Server 2005

I also think the tools for SQL Express are a little bit less good that the full version, but it doesn't make much difference. The free versions have been released pretty much as a competitor to mySQL.



fhenkel -> RE: Suggestions? (5/6/2006 11:16:46)

yb2, thanks for the infomation. Let me ask this quesion then. I have been using the MS Access as the database and an a bit familar with it and building and maintaining it for my purposes. Mostly I chose it because it has a GUI interface and therefore is similar to FP for me to use. While I understand the MSDE will work but is a cut down version of SQL2000 but I don't believe it has the WYSIWYG interface, is this not correct? Keep in mind I know nothing about the SQL2000 except that it or MSDE is required for SharePoint, which I no longer use now that I've retired and no longer maintain the office SharePoint websites. Most of my "hobby" site work is with building a "FP Extensions" type of site or a ASP/Access site.



Spooky -> RE: Suggestions? (5/6/2006 11:40:24)

There are various web based tools you can use to setup and maintain MsSQL databases - its only a small step to become proficient.
You would use a similar system (such as phpMyadmin) for mySQL anyway



yb2 -> RE: Suggestions? (5/6/2006 11:48:32)

if you have Access 2003 then you can use it as the GUI for SQL Server 2000/MSDE, by using an Access Data Project file .adp

If you can, move to MSDE/SQL Express because it will beat the pants off Access.



Doug G -> RE: Suggestions? (5/7/2006 3:02:38)

fwiw, on my XP Pro development box I run sql server 2000, mysql 5.0, php5 with IIS, Apache, Frontpage, Visual Studio, all simultaneously, without any conflicts.

I've been using MySQL Administrator for MySQL administration, it's very similar to SQL Server Enterprise Manager.



fhenkel -> RE: Suggestions? (5/7/2006 10:02:52)

I have downloaded the SQL Server 2005 Express Edition. I also downloaded the SQL Server 2005 Management Studio Express. Would this be basically all I'll need to switch from using Access 2003 to SQL as far as interfacing with the SQL? Also I assume that the Server Express goes on the server and the Management Studio goes on my development machine, correct? I need to get this going asap since I just took on a Paint horse Ranch site which keeps track of al kinds of data on each of their horse for sale. You got to love it when business comes in from just word of mouth.

YB2, could you elaborate on using the Access 2003 for the interface with SQL?

Oh, just so you guys know, I have gotten several of the ASP and SQL For Dummies eBooks so I don't have to bug you all with so many basic questions. Thanks to all for the input so far.



yb2 -> RE: Suggestions? (5/7/2006 11:09:49)

quote:

Also I assume that the Server Express goes on the server and the Management Studio goes on my development machine, correct?


Is your development machine a dummy of the main server? If so, I'd put Express on the dev machine with Management Studio, and put Express on the main server too. Then build your database on the dev machine, and when you are ready to let it go into the world detach it from the dev machine, move the detached file to the server, and attach it.
Read this on how to attach/detach using the Object Explorer in Management Studio http://msdn2.microsoft.com/en-US/library/ms190209.aspx

This is some stuff on adp and setting it up. It refers to SQL 2000 all the way through but it should work with 2005 - not that I've tested it myself!
http://office.microsoft.com/en-gb/assistance/HP052731031033.aspx

I just tested it, and it worked. I picked File > New, then Project using new data... from the sidebar. Name the file and save it where you like. Then a wizard starts, fill out the fields, click Next and Finish and it's done.

Having said all that, Management Studio is very nice too, and you can do everything you want from there, so perhaps you don't need adp after all?



fhenkel -> RE: Suggestions? (5/7/2006 11:26:20)

YB2, thanks again for the info but I just tried installing the Express on my server after shutting down the SQL2000 service. It starts installing the Client portion and comes up with a "fatal error 1603" and can't continue?? I have found that error all over the web referring to SQL 2005. The event viewer shows a error of 2203 also from the Installer. I have included the Log file below. I have bolded the error line. Any ideas?

=== Verbose logging started: 5/7/2006 9:50:03 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:\WINDOWS\system32\msiexec.exe ===

MSI (s) (D8:6C) [09:50:09:332]: Product: Microsoft SQL Server Native Client -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2203. The arguments are: C:\WINDOWS\Installer\52911ed6.ipi, -2147024629,

MSI (c) (C0:FC) [09:50:10:443]: MainEngineThread is returning 1603
=== Verbose logging stopped: 5/7/2006 9:50:10 ===




yb2 -> RE: Suggestions? (5/7/2006 11:34:56)

Can't be sure what it is, but I think it's something to do with having a full SQL 2000 on there already.

I'd make a backup of any SQL 2000 databases you have - you'll need to restart the service, and backup the model and master too - and then remove SQL Server 2000. Run the latest service pack for Server 2003, and then try again.




fhenkel -> RE: Suggestions? (5/7/2006 11:37:30)

I forgot the Summary Log.


Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790)
Time : Sun May 07 09:49:46 2006

Machine : DFH03
Product : Microsoft SQL Server Native Client
Product Version : 9.00.2047.00
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_DFH03_SNAC.log
Last Action : InstallInitialize
Error String :ipi
Error Number : 2203
--------------------------------------------------------------------------------
DFH03 : There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information.



fhenkel -> RE: Suggestions? (5/7/2006 11:47:48)

I was afraid you'd say that. I'll backup first and then try the uninstall of SQL2000. I'll also try downloading another package of Express since it did refer to a possible package corruption.



fhenkel -> RE: Suggestions? (5/8/2006 10:26:57)

Well it seems I was wrong about which version of SQL Server I had installed when building the Web Server. I looked in Add/Remove Programs and it wasn't SQL 2000 after all, it is MSDE for Sharepoint. I forgot I had rebuilt the server after a crash and selected to go with the MSDE for my purposes. One problem I'm having in connecting to that SQL server is that it says it does not exist or access denied? I'm trying to access it from my workstation which is the development machine. I've read, on the web, that the default for the SQL server is to not allow remote connections, would anyone know about this and how I change it.




yb2 -> RE: Suggestions? (5/8/2006 10:30:55)

Are you using Windows or SQL authentication?



fhenkel -> RE: Suggestions? (5/8/2006 13:07:06)

Windows NT but keep in mind that the SQL was installed automatically when I Installed SharePoint so I didn't get to set up anything to do with MSDE. I have installed Studio Management Express and it tells me that most of what I'm looking for isn't supported by SQL2000 (MSDE). I still looks like I need to uninstall the MSDE and install the SQL 2005 Express.

According to the SQL 2005 Express install on my development machine it defaults to TCP being disabled and I used the configuration manager to enable it. I'm wondering if the MSDE has TCP disbaled also and how to turn it on so I can access the MSDE from my development workstation.

All that said I'll just remove the older MSDE and install the new one. I'm not really interested in keeping the sharepoint databases but I backed them up already by simply copying them out to a backup..

I really appreciate your assistance to this point.



yb2 -> RE: Suggestions? (5/8/2006 13:13:46)

No probs.

Personally, I found MSDE a real bugger to install, whereas Express is much much better packaged. I didn't realise Express had TCPIP disabled as default, so thanks for that tip.

I don't think MSDE has TCPIP disabled by default, it could be the authentication model, it could be setup under an instance. Could be anything really! Especially if you didn't set it up.



fhenkel -> RE: Suggestions? (5/8/2006 13:27:13)

Well it looks as if we're up and running with Express. It was the fact that MSDE was already there. After removing it the install of Express went fine. I'll reinstall the management Studio also now.

I'll also take alook at your link to "Attaching a database" just to see if I can get the SharePoint stuff back in there but so far it doesn't look like I've lost anything along those lines.

The only item on the install was a warning that the hardware does not meet their requirements but it complated the install. It will figure if I need to have to buy another bigger machine for the server.



yb2 -> RE: Suggestions? (5/8/2006 13:30:00)

Express is capped at using 1GB of RAM and 4GB of harddisk, so as long as you've got those I wouldn't worry. Make sure you've got v2.0 of .NET installed on the server too.



fhenkel -> RE: Suggestions? (5/8/2006 13:51:47)

YB2, FYI.
Here is the notice screen which comes up at the end of the install. It mentions about the TCP connections being disabled.


Configuring and Managing SQL Server Express
ยท For improved manageability and security, SQL Server 2005 provides more control over the SQL Server surface area on your system. To minimize the surface area, the following default configurations have been applied to your instance of SQL server:

o TCP/IP connections are disabled
o Named Pipes is disabled
o SQL Browser must be started manually
o OPENROWSET and OPENDATASOURCE have been disabled
o CLR integration is disabled
o OLE automation is disabled
o xp_cmdshell is disabled

To enable or disable features and services, run the SQL Server Surface Area Configuration tool from the Start menu.



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.125