SQL Server 2008

[blackdragonsdg]

I was wondering if anyone has tried using SQL Server 2008 in place of MySQL for their database? If so, are there any pitfalls to be aware of? I would think compatibility might be an issue as it was with MySQL versions.

I was thinking about trying it but I thought I would ask here and see if anyone had any advice for or against the idea.

[image]

Last I checked it was made for mysql, are you talking about Microsoft SQL? Then I really don't think thats going to work

[blackdragonsdg]

Yes, I was referring to Microsoft SQL Server 2008.

[Andrew80k]

You could probably get it to work, but it would take a bit of work. You'd have to look at the database stuff to see. It's not really abstracted out completely though. You could likely use any database you wanted but you'd pretty much have to do the work.

[blackdragonsdg]

So after about four hours of tinkering around with SQL Server 2008 I am not having much luck even getting the database to import/source in. For some reason the program doesn't want to use .sql files it wants .txt or .csv and I have never heard of .csv until today. I think I am way outta my league on this idea.

I think SQL Server 2008 would be much more useful in hands of an experienced database administrator. Seems to have lots and lots of tools and a whole bunch of other gadgets I don't know what to do with.

[So_1337]

.csv files are simply comma separated values. It's a popular export method for a lot of Windows-based programs like Excel, Access, and MySQL.

I've gone through the work before of exporting entire tables from MySQL into .csv, opening them in Excel, adding a blank column before all the information, and then using it to write queries. From there, I just copy the whole deal into a text file, save it as a .sql file, and source it in. So for most tables that are just simple integers or text, that would work for you, though it'd take some work. I have no idea how you'd handle anything like the player profile or blobs.