Search Results

In SQL server, triggers operate on a batch of records. All too often developers think they only need to handle one record inserts, updates or deletes. …

Underscores are not evil just harder to type. What is bad is changing standards midstream without fixing all the existing objects. Now you have personId, Person_id, etc. and can't remember which table …

And further if you don't learn the simple SQL in the easy crud stuff, how will you ever get to the point where you can write complex SQL for reporting? … I also see many questions about how to do something using an ORM that the poster already knows how to do in SQL. …

But one thing I would require of anyone who will be writing SQL is knowledge of joins and when to use a left join vs. an inner join. …

They are deprecated in SQL Server and in fact do not return correct results realiably even in the older versions. … No query that needs an outer join should contain the implicit syntax in SQL Server. …

Personally I try to do such a good job of defining the data needs that user defined fields and tables are not necessary. If you haven't defined 98% of what they would need, in most cases that means yo …

If you need a performance tuning dba, then ask questions about tuning - find out what they have done and how much it increased performance. Dbas who can't tell you metrics on performance improvements …

I would never consider using the designer to write my queries. I know my database schemas in great detail (and our databases have hundreds of tables) and don't have to think about how to join to them, …

happy because they don't heve slowdowns once a month whe the reports run and the BI people are happy because they always have work to do and becasue they get paid better than someone who just writes t-sql …

I think it would be poor design to not use the database for the things it is meant for. I have never seen any database where the rules were enforced outside the database that had good data. And I have …

If I have dynamic SQL that when I use the @debug and in this case I print the sql instead of executing it, so I can check the SQL statement produced. … (Note the table variable temp table stuff is SQL Server specific, I don't know if this will work with other databases.) …

Foreign Keys are not indexed automatically in SQL Server and I imagine they aren't in most other dbs either. …

If you never learned basics, how can you expect to start learning SQL with the advanced stuff? You won't understand enough to even start. … ORMs in the hands of a person who understands SQL - a good tool. ORMs in the hands of someone who deosn't know SQL at all - disaster waiting to happen. …

This means no dynamic SQL of any kind (including in procs). That way users who directly access the database can still only do the things they are allowed to do by the application. … There shoud be no SQL Server logins. Instead the users should be in windows groups that are given rights based on what they are allowed to do. …

It is just that most application developers aren't SQL specialists. However, is saving the devs time to get better at SQL really a plus? …