2,544 reputation
712
bio website
location
age
visits member for 3 years, 2 months
seen Nov 3 at 14:13

Mar
29
comment SQL Server Change Tracking
I certainly hope you are updating your resume, you are going to need it.
Mar
28
comment Need help with long running query
Let's see, implicit syntax, no indexing, dirty reads, correlated subquery. The people who wrote your application are clearly incompetent and I personally would buy a new one and insist on getting my money back. There is no hope for this one since they have clearly had no idea about basics.
Mar
22
answered New Database vs New Table for User Registrations
Mar
20
comment help with simple sql queries
USING will not work on all databases. Since he did not specify it would be far better to use the more common ON clause. Espcially someone with this level of knowledge (i.e. none at all, needs to learn the ON clause first)
Mar
20
comment help with simple sql queries
Never use implicit joins, they are a SQL antipattern and if you are just learning it is even more important to learn to use explicit joins so that you understand what you are doing.
Mar
20
comment Database and query optimizacion
What you have right now is in no way large. This is teeny tiny for a database. Queries shoudl run in milliseconds against somethign this small. However, I would suspect some of your problem is that you are either returning too many records due to insufficient where clasues or you have failed to index the tables.
Mar
18
answered Database Design Relationship for Patient Visit in MS Access
Mar
15
comment Database Design question, calculate or save financial positions
You probably want to do some reading on temporal database design.
Mar
15
comment Database Design question, calculate or save financial positions
I would calculate the owed amount and just store each payment as it comes in. And for anything that is precalculated that could change that you decide to store for performance resons, make sure you havea trigger to keep the data in synch and it is porbably a good idea to havea job that is run nighlty or so to do the updaetes in case anything bypasses the trigger (such as a bulk insert process).
Mar
15
answered Database Design question, calculate or save financial positions
Mar
15
comment SQL server performance and tuning
Step one hire a dba with experience in large systems. This isnot some easy questions that someone on the InNternet can answer. Likely there are many things including redesigning your database or rewriting your queries or redoing your indexes or updating your statistics that need to be done. You may need to look at partioning the data and hardware changes.
Mar
15
answered PRIMARY KEY CONSTRAINT fundamentals
Mar
14
comment Right Join vs Left Join - My joins are broken and I don't understand why
In almost every case where I have seen people use @@error they have neglected to test after every indivudal piece of code and the person wonders why the errors are not stopping the proc. I refuse to pass a code review when it contains @@error.
Mar
14
answered Right Join vs Left Join - My joins are broken and I don't understand why
Mar
12
comment SQL update set column = @ parameter
ID = (SELECT HouseNo,ID FROM Table2 t1 JOIN UserAttribute t2 ON t1.ID =t2.UserID WHERE HouseNo = @HouseNo) will error becasue you are selecting two fields and not one.
Mar
8
comment Complex query with multiple normalized fields
I would suggest that before you do any datbase designing work (and you need to - this design is atrocious) that you read amazon.com/SQL-Antipatterns-Programming-Programmers-ebook/dp/…
Mar
7
answered Large time difference between two almost identical simple queries…why?
Mar
6
comment Migration advice from SQL server 2000 bak
You do have a database backup not just a server backup, right?
Mar
5
comment When using an ORM, what are some things to watch out for in your database design
And consider putting very complex logic in a stored proc. ORMs can call stored procs and for very complex logic, it is easier to performance tune a proc.
Mar
5
comment When using an ORM, what are some things to watch out for in your database design
Id is a SQL antipattern for naming the id field and should not be used.