meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 8 months |
| seen | Jun 7 at 21:42 | |
| stats | profile views | 125 |
|
Feb 25 |
comment |
Version control for database objects The key to devloper discipline is not allowing them to move objects to QA or Prod (which frankly they shouldn't be doing anyway)and the people who do have the rights will only move from your source control. |
|
Feb 25 |
answered | SSIS Validation slow. OLTP OLAP running on same server |
|
Feb 20 |
comment |
NoSQL, CouchDB vs. CouchBase, What should i do? And of course check and see if you really need to return the entire data set. Poor practices such as using select * when you should specify only the fields you need (and if you have a join, there is a 100% chance there is a field you don't need.) or returning a million records to a web site at once when no one is going to look through them all are things that can cause problems and are easy fixes. |
|
Feb 19 |
comment |
How to design future proof tables? The traditional way to do it is to create additional columns custom_1, custom2, etc, up to ten of them and then let the customers use those. It is a rare customer who would need more than ten columns to customize. EAvs are only useful if you willhave many fields thatt can't be defined at design time (such as fields for lab tests). THey scertainly shoudl not be a substitute for failure of teh devs to do due dilgence and find out what fields are needed which is the most common current use. |
|
Feb 19 |
comment |
Query is not using indexes on third table in left join Data fiels you intend to join should be designed from the start to use the same datatype. Anytime you are converting in a join you are harming your performance. |
|
Feb 19 |
comment |
Query is not using indexes on third table in left join You should not combine implicit and explicit joins either. I don't know about mysql but I have seen incorrect results from that in SQl server as it confuses the optimizer. Of course you should not use implicit joins period as they are a SQL antipattern and were replaced in the last century. |
|
Feb 19 |
comment |
How to design future proof tables? EAV is the worst choice for design unles the data changes are totally unpreodicatble. It is far better to adjust the schema when you need new fields. EAV are performance killers. |
|
Feb 18 |
comment |
SQl Server 2008 R2 - sa can login but not access database You aren't actualy using the sa password to log in from the application are you? That is a security hole that MUST be immediately fixed. |
|
Feb 18 |
comment |
Create a VIEW that spans 3 tables Well I would start by never using implicit joins under any circumstances. That is a SQL Antipattern. |
|
Feb 18 |
comment |
Which is better: identity columns or generated uinique id values? So using his way, on dev I am at record 1000 and I add a test record and get 1001. I then want teh prod data which is at 2000. Seemes like I still havea conflict for record 1001. There is NO ADVANTAGE to creating your own numeric values except not having gaps which ioccasionally needed for regulatory or legal reasons. It is also really easy to get it wrong and have run conditons that cause you to lose data integrity when you roll your own. |
|
Feb 18 |
comment |
Which is better: identity columns or generated uinique id values? @jcolebrand, you don;t move the data, you restore the data from teh prod backup. Then you don;t have tow erroy about it. Of course you do then have to run the scripts to make all the changes that haven't gone to prod yet, but they are in source control (right?) and thus easy to run. |
|
Feb 14 |
comment |
How could DBAs be more 'programmer friendly'? Of course the opposite question should be asked as well, How can programmers be more dba friendly. |
|
Feb 14 |
comment |
How could DBAs be more 'programmer friendly'? I think those two threads should be required reading for both application devlopers and database people. |
|
Feb 14 |
answered | How could DBAs be more 'programmer friendly'? |
|
Feb 14 |
comment |
Have @Table1 with values to update into @Table2, can I update @Table1 with @Table2.@@Identity? or Cursor? I'd look into the output clause if I were you. And never ever use @@identity, if you must do it one record at a time, then use scope_identity() |
|
Feb 12 |
comment |
Identify NON-ANSI joins in SQL Server 2008 R2 on a Database that's in 2000 (80) compatibility mode I just wanted to be sure you knew that waht the query was actaully doing might not be what you were expecting it to do. But yes you are in for a tedious few weeks. |
|
Feb 12 |
comment |
Identify NON-ANSI joins in SQL Server 2008 R2 on a Database that's in 2000 (80) compatibility mode Did you know that even in SQL Server 2000, you should not use these joins as they often give the wrong answer. Somtimes they can get interpreted as cross joins instead of outer joins for instance. When you convert I would carefully check to ensure that your new version gives the same results as the old version. You may not have been doing the join you thought you were doing. |
|
Feb 8 |
comment |
INSERT trigger dying with with #target columns not equal to #expressions, but they are equal just for giggles check and see if dash_pre_queue has any triggers |
|
Feb 8 |
awarded | Organizer |
|
Feb 8 |
revised |
INSERT trigger dying with with #target columns not equal to #expressions, but they are equal edited tags |
