Viewing 15 posts - 21,211 through 21,225 (of 22,224 total)
You've already laid out the issues pretty well. You can either save it in the database where:
[highlight]You get a good, clean, synchronized backup
When the user is deleted, you also easily...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 22, 2008 at 5:52 am
You could use a view to combine the data from the four tables into a single select statement. 12,000 rows, depending on how much data is in them, is not...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 22, 2008 at 5:44 am
I have to agree with Steve on this one. If you've had a conflict (and who hasn't) and that comes up in an interview, you need to be honest about...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 22, 2008 at 5:27 am
this is a pretty regular debate. I usually fall back on business requirements to help decide.
The one technical issue that does help decide is backups. If you store the...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 21, 2008 at 11:55 am
Well, there you go. Trigger is the trick then.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 21, 2008 at 11:50 am
You don't have to use a trigger.
You could use the OUTPUT clause from the insert statement:
INSERT INTO TabA (Col1, Col2)
OUTPUT Inserted.Col1, Inserted.Col2 INTO TabB (Col1,Col2)
VALUES ('A','B')
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 21, 2008 at 11:46 am
Because of the naming conventions (you're right, they're horrible), it's hard to tell exactly what's happening in the "generic" design. However, looking at your design, it sure seems to me...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 21, 2008 at 7:33 am
Congratulations.
Yes, you should learn tons & tons. When you've only yourself to rely on, you start learning things very, very quickly. Remember that automation is your friend. Spending an hour...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 21, 2008 at 7:16 am
The only time I had to do this I was using an application to take the output from a stored procedure and then save it to a file. I haven't...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 21, 2008 at 7:05 am
Sandy (1/20/2008)
Hey Grant,Thanks for your trying,
did you get any way to solve this?
Cheers!
Sandy.
I'm sorry, no, becuase, I think like everyone else, I still don't understand what you're trying to accomplish...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 21, 2008 at 6:17 am
If I understand the question, you can simply use the Database Diagrams to see all the tables and their relationships. Assuming those relationships in your database are all through primary...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 18, 2008 at 10:32 am
D'oh!
Did Steve see?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 18, 2008 at 8:43 am
And following up on what Matt says, you want to know that too. Except for extreme circumstances (you're about to lose the house, the family is hungry, etc.) lying your...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 18, 2008 at 8:42 am
Bad news. I just ran this little in 2008:
goto MyLabel
exec sp_who
Mylabel:
It's STILL there. I'm planning on being in Seattle in November for PASS... I'll brink an Ozark Tire Thumper and...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 18, 2008 at 8:24 am
I agree. We work with XML a lot out in the applications, but the database mostly just returns regular old result sets.
However, if you really had to, in addition to...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 18, 2008 at 8:13 am
Viewing 15 posts - 21,211 through 21,225 (of 22,224 total)