Viewing 15 posts - 181 through 195 (of 1,553 total)
There's no way for the SQL Server to know what USERNAME is set to at the calling clients workstation, unless that host sends that info along to SQL Server.
When you...
October 10, 2007 at 6:22 am
The pros and cons of procedures can fill entire books, but in general, I'd say that the concensus is that stored procs are a 'good thing'.
However, it's a tool like...
October 9, 2007 at 7:49 am
There's nothing wrong to construct a query based on whatever the userinput is, then when the query is known and complete, just run it from the app.
There's no particular need...
October 9, 2007 at 3:41 am
A few 'big deals' that comes to mind:
- opens risk of injection (ie one needs to deal with it properly)
- violating security models/policies (ie is it kosher to grant access...
October 9, 2007 at 3:33 am
Seems like the confusion is about how to enter the date into the variable?
And also maybe combined with confusion on how a datetime is presented when retrieved from a variable...
October 9, 2007 at 3:19 am
If an order by in a view is 'sense' or 'nonsense', that's a theoretical question.
According to theory, if we want a table, then there is no order.
If we have order,...
October 8, 2007 at 8:44 am
A torned page detected is a sign of hardware malfunction or some other unexpected event preventing a write to the database to complete in a clean way.
If you depend on...
October 3, 2007 at 7:45 am
Don't know if this makes it any clearer...
In master you have the login, and the login has the password.
In the user db you have the user, and the user...
October 3, 2007 at 7:37 am
My personal favoite is xpsmtp
http://www.sqldev.net/xp/xpsmtp.htm
No, MAPI, no Exchange requirements, no funky stuff, just plain simple SMTP 😀
/Kenneth
October 3, 2007 at 7:30 am
Deadlocks is a 'bad design' issue, not a performance issue per se.
It's 'fixed' by re-designing the process that is found to be the cause.
What about disk-configuration?
Does the box have a...
October 3, 2007 at 7:24 am
Could be a number of different reasons...
Go to Google, type in 'SQL Server error 17803 Insufficient Memory Available' and see if any of the results apply to your situation.
/Kenneth
October 3, 2007 at 7:18 am
This is a severe error, and indicates that the db is likely in an incosistent state (suspect/corrupt)
-- quote BOL --
If a torn page is detected, an I/O error is raised...
October 3, 2007 at 7:03 am
bledu (10/1/2007)
if you want to do that stuff the way you want i think you are better...
October 1, 2007 at 8:50 am
My guess is the errormessage in this case would be 'screaming developers' or similar 😀
October 1, 2007 at 8:42 am
Could you please post the DDL for these two tables?
(and perhaps also with a few sample rows that shows what the actual data look like)
I'm not quite getting how they...
October 1, 2007 at 6:38 am
Viewing 15 posts - 181 through 195 (of 1,553 total)