network profile
| bio | website | windows7-issues.blogspot.com |
|---|---|---|
| location | Oregon | |
| age | 33 | |
| visits | member for | 8 months |
| seen | Feb 15 at 21:06 | |
| stats | profile views | 12 |
I recently got my B.S. in Business Information Systems and am just starting my career as an Database Developer / IS Engineer / however you like to call what I do, lol. After completing my first internship I've already gained a tremendous amount of experience and insight into the corporate environment. I generally work 45-50 hours a week, and challenge myself to expand on my skills.
I'm grateful for all the people on SO who've been so helpful to me in the many questions I have. I hope to continue to become a more valuable member of this community and in the near future be a more experienced contributor in the areas of web design, database design, and other miscellaneous cool techie stuff :)
Cheers!
|
Jan 28 |
accepted | Conditional WHERE clause |
|
Jan 28 |
comment |
Conditional WHERE clause Brilliant use of COALESCE! I would have never thought of that. :) I also added set @filter = nullif(@filter,'') just before that to ensure an empty string is never passed in which would create an invalid SQL statement. I also if object_id(N'tempdb..#tbl') is not null drop table #tbl before the #tbl create to ensure I'm starting with a clean slate. |
|
Jan 28 |
comment |
Conditional WHERE clause I probably should have stated that I would LIKE to use a table variable because I prefer to keep my SQL clean rather than dealing with a bunch of temp table cleanup and if-else statements. |
|
Jan 28 |
comment |
Conditional WHERE clause @StrayCatDBA For future reference, would this create a permanent defined type in the database? Server? Thanks for the answer anyway! :) |
|
Jan 26 |
asked | Conditional WHERE clause |
|
Jan 11 |
comment |
SQL Server Event Alerts Lack Enough Details @mrdenny That's very unfortunate. This level of error logging is completely useless to me then as it provides no means of investigation the cause of said errors. Why is virtually everything about SQL Server Administration so disappointing until 2008 and above? :( |
|
Jan 10 |
comment |
SQL Server Event Alerts Lack Enough Details @mrdenny SQL Server 2005 |
|
Jan 10 |
comment |
SQL Server Event Alerts Lack Enough Details @MitchWheat For example, the Server they were trying to login to? What application were they using? Etc. In this case the user is a utility account which is using SQL Server authentication and is used for many of our applications to connect to various databases. |
|
Jan 10 |
asked | SQL Server Event Alerts Lack Enough Details |
|
Dec 19 |
awarded | Commentator |
|
Dec 19 |
accepted | Securely Send Database Mail via an Insert Trigger |
|
Dec 19 |
comment |
Securely Send Database Mail via an Insert Trigger @CadeRoux Wow! I had no idea SQL Server actually had built-in EmailQueues, I was reading up on them and they're FAR more robust than our queue tables. Wish I had time to re-architect our whole email paradigm, but alas I have only 2 days left so it will have to be the quick fix for now. :( Thank you so much for all your wonderful advice. :) |
|
Dec 19 |
comment |
Securely Send Database Mail via an Insert Trigger @CadeRoux You make a great point, as did Aaron. I just preferred it to act like an Exchange server where email is nearly immediate. Still, good advice, and thank you so much for the speedy reply. Just one last thing. While in the queue, how would you recommend I indicate whether the email was already processed? With the trigger I set a field containing the mail_id and checked that against the sysmail_unsentitems table. Good idea? |
|
Dec 19 |
comment |
Securely Send Database Mail via an Insert Trigger @CadeRoux I failed to mention, but this is all within the context of an Intranet, so the email really is instantaneous. That's not necessary per say, but helpful. Also, wouldn't it be a lot of overhead to have a job run every minute or five?... Ooh, I just thought of another idea. What if I wrapped sp_send_dbmail in a separate stored procedure and called that from the trigger? I suspect I'd run into the same issue though. >.< |
|
Dec 19 |
comment |
Securely Send Database Mail via an Insert Trigger However, in this way I cannot send email immediately, correct? If so that's very unfortunate, but it seems like you are making the point that that would be a good thing for load management? |
|
Dec 19 |
asked | Securely Send Database Mail via an Insert Trigger |
|
Dec 12 |
comment |
Msg 7391, Distributed Transactions (DTC) on SQL Server Unfortunately my infrastructure team shut me down on this for now because they are too overloaded, but hopefully I will have a chance to come back to it in one month. If not, I will assume this is a correct answer based on the positive ratings from other users. At any rate, thanks so much for your answer. :) |
|
Dec 12 |
comment |
Msg 7391, Distributed Transactions (DTC) on SQL Server @MarkStorey-Smith I've actually Google'd several different parts of the message, but the particular issue I was having seemed too convoluted and I was having trouble finding an answer that applied to me. I think your answer might help though. I'll definitely give that a try when I get back to the office and let you know how it goes. Thanks. :) |
|
Dec 12 |
comment |
Msg 7391, Distributed Transactions (DTC) on SQL Server @swasheck My heavens YES! lol, I would never ask here without having done due diligence first. Even Pinal says this particular message can arise from many different causes. :) |
|
Dec 12 |
asked | Msg 7391, Distributed Transactions (DTC) on SQL Server |
