Jan 13
Just saw this. MSSQLTips.com was asked: "Is Microsoft SQL Server superior to MySQL or not? What are the pros and
cons of using SQL Server over MySQL? Is MySQL mature enough to compete
with a big player like Microsoft and Oracle? Can we fairly compare both
products?"
Read their answer @ http://www.mssqltips.com/tip.asp?tip=1920&ctc.
Nov 12
Sometimes, IDENTITY seeds get messed up, especially after a db restore, so this script comes in handy. It even gives a little report on what the previous value was and what the new values is. For tables that don't have IDENTITY values, it gives a clean error and skips them. Nice and easy.
Sep 30
A lot of times we take functions like valueList for granted. When it comes to SQL Server, if we wanted to do something similar, we have to jump through a lot of hoops.
Fortunately, I stumbled upon an article covering different techniques on MS SQL 2008, 2005, and 2000.
Take a look, you won't be disappointed.
Read more @ http://code.msdn.microsoft.com/SQLExamples/Wiki/View.aspx?title=createacommadelimitedlist.
May 7
Has anyone worked with a solid SEO firm that they can recommend?
Apr 7
So I decided to try out CodexWiki. It looks really good, and built
by two people I trust: Mark Mandel and Luis Majano. However, I don't
like MySQL to be quite frank, and that is the only DB supported at this point. More on that later.
I downloaded CodexWiki, and looked at the db install notes here: http://www.codexwiki.org/wiki/Installation_Guide.cfm#Database_Installation
What?! I couldn't decipher what exactly to do. So I thought maybe I
could convert the SQL script (which is MySQL only) to SQL Server, but I
found there wasn't an easy way to do that either. I used various
tools, but each one's output was incomplete. So I gave in after 6
hours (if you look at the script, you'll see why), and installed MySQL. Which was surprisingly easy. However,
finding a good MySQL Client was harder. I did find one, but
found according to the instructions that you couldn't run the SQL
script from a client!
Now what! So I went looking for the SQL
Script, and that wasn't very well documented either. I finally found
one that looked promising in the \codexwiki\workbench\sql\0.5
directory. It was called codexwiki_mysqldump.sql.
I then did some quick Scroogling and adapted a script to install the dump. Here are the steps.
- Use a client to create a "codex" database.
- Open the command prompt. (Hopefully on Windows, you checked the
option to put MySQL in the PATH, so you can run MySQL commands very
easily.)
- Go to the directory mentioned above. Run this command: mysql -u root -p codex < codexwiki_mysqldump.sql
- Enter the password for the server at the prompt, and that should be it.
Hopefully that helps! Maybe CodexWiki will support SQL Server with a proper script in the near future.
1-13-2010
1-13-2010
12-17-2009
12-14-2009
12-3-2009