205 reputation
15
bio website improvingsoftware.com
location United States
age 43
visits member for 3 years, 3 months
seen Jun 23 at 17:26

Development Manager. Software Developer. Texan.

You can follow me on twitter at: http://twitter.com/johnfx


May
5
comment Will adding more indexes speed up using RedGate SQL DATA compare?
DO you mean SQL Data Compare? SQL Compare wouldn't be affected at all by indexes as far as I can think of since it only operates on the definitions of objects and not the data itself. In any event, I think you are barking up the wrong tree.
May
8
awarded  Commentator
May
8
comment Saving a SQL Server database to a file and opening it on another server under any database name
You can move the MDF file and attach it on the other SQL instance, but I'm afraid that is no simpler than backup restore. Just bite the bullet and go with it. More complexity is the price you pay for using a more enterprise database backend. Check out the DBA stackexchange site or the MSDN documentation for how to do this.
Jan
12
comment MySQL large databases, unique index effect on efficiency?
FWIW: 300K rows is not a big database.
May
13
awarded  Yearling
May
12
comment when to use technology like hadoop?
You scale when the current software isn't meeting demand. Not sure if there is a better answer than that.
May
12
answered Merging two Access DB's
May
12
awarded  Critic
May
12
comment Merging two Access DB's
I agree with Remou. Everytime someone says that MS Access wasn't designed to do (some simple thing) I hear "I don't know how to do (some simple thing) properly in Access therefore the problem is Access"
May
12
comment when to use technology like hadoop?
What do you mean by scaling? Adding hardware? Changing RDBMS software?
Jan
24
comment Database design for a time tracking application
That was a reference to your comment "The first three columns are the PK", that's all.
Jan
24
comment Database design for a time tracking application
I've built a few timesheet apps in my time, and let me just add one tweak to this. Use a surrogate identity column for the PK instead of a composite key. In every system I've worked with there is always a need to communicate outside the system about specific time entries and it is easier to just use a reference number than a three part identifier. Also, the time entries tend to get joined a lot (for example to invoices) and you will get better performance joining on a single integer field.
Jun
6
awarded  Supporter
Jun
6
comment What are the consequences of setting varchar(8000)?
Those types don't contribute as much to the 8K row size limit on a table because the actual data is stored in a separate table under the covers instead of inline with the rest of the columns. There is still a performance impact, but for different reasons. There are also limitations on feature support on these fields when compared to varchar and nvarchar
Jun
4
awarded  Teacher
Jun
4
answered What are the consequences of setting varchar(8000)?
Jun
4
comment What are the consequences of setting varchar(8000)?
What DB platform?
May
13
awarded  Autobiographer
Feb
28
comment SQL Server tempdb question
@Abe Miessier - Updated my answer to address that.
Feb
28
answered SQL Server tempdb question