Viewing 15 posts - 5,086 through 5,100 (of 7,636 total)
In order for ownership chaining to work there are 3 more things that must be setup that I have not heard you mention yet:
1) the source database must be TRUSTWORTHY
2)...
October 24, 2008 at 12:13 pm
balv (10/24/2008)
October 24, 2008 at 11:55 am
I know that in SQL Server 2000 w ODBC SQL Logins were not encrypted. I am not sure if that is still true for SQL Server 2005 and/or ADO.net...
October 24, 2008 at 11:48 am
Possibly the maintenance jobs are failing part way through?
October 24, 2008 at 11:45 am
Colin Macguire (10/24/2008)
October 24, 2008 at 11:06 am
I really don't think that there is much that you can do here with this approach. You need to get the customer to tag them appropriately in the table.
Otherwise,...
October 24, 2008 at 10:55 am
I am not sure that there is any safe way to "Kill" the cmd.exe. I really think that you need to fix your Task.exe so that it works correctly...
October 24, 2008 at 8:47 am
As I recall, here is how you convert:
1) Place all WHERE clause comparisons in the order which their tables occur in the FROM clause. For instance, since "v" occurs...
October 24, 2008 at 8:42 am
anvieph (10/24/2008)
October 24, 2008 at 8:23 am
I agree with Mahesh, this would be better (and easier!) as a stored procedure.
October 24, 2008 at 6:14 am
Glad I could help.
And definitely test this. I doubt very much that I got this right the first time.
October 23, 2008 at 10:39 pm
Your terminology is not really correct here. What you are calling "Ansi" syntax, is in fact ANSI SQL-89 syntax. What you are calling SQL Server 2005 syntax is...
October 23, 2008 at 10:35 pm
If the program is waiting for input from the command pipe that the SQL process used to issue the command, then a Control-C may cause it to exit. Now...
October 23, 2008 at 9:59 pm
Viewing 15 posts - 5,086 through 5,100 (of 7,636 total)