Viewing 15 posts - 2,551 through 2,565 (of 2,647 total)
Is this homework? If not, the "requirement" should be suggested to be changed for efficiency 🙂
Jared
September 15, 2011 at 2:49 pm
Something "seems" not right here... Why is your BEGIN TRAN inside of the TRY? I am not saying it is wrong, but I have never seen it done this way...
September 15, 2011 at 2:45 pm
Sean Lange (9/15/2011)
September 15, 2011 at 2:35 pm
I'm no expert in this... but I don't see any commit on your transaction. Only rollbacks.
Thanks,
Jared
September 15, 2011 at 2:19 pm
What is the code from abc_specialty1_sp? You may need to use a SAVEPOINT in your "nested" procedure. This way you can rollback to that without resetting the Transaction Count.
See http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=37247#112267
Thanks,
Jared
September 15, 2011 at 2:03 pm
This seems especially programmatic for SQL. Is there a reason you are doing this all in an sp instead of programmatically? I'll take a look at this in the meantime...
Jared
September 15, 2011 at 1:56 pm
I am not completely sure, but this link is great for learning about policy management: http://www.databasejournal.com/features/mssql/article.php/3739386/Policy-based-Management-in-SQL-Server-2008-150-Part-I.htm
Also, a suggestion is to not have each developer have their own login. Set...
September 15, 2011 at 1:48 pm
The better description is it has to be divisible by 2, but > 2. i.e. 2 drives cannot be RAID 0+1, but 4, 6, 8, 10, etc. can all...
September 15, 2011 at 12:52 pm
🙂 That's probably a very good idea!
Jared
September 15, 2011 at 12:33 pm
All article with reference to HasAccess refer to a login being granted access to login to SQL Server. This leads me to believe something is wrong with the SQL...
September 15, 2011 at 11:45 am
Also... Try running this statement:
USE DatabaseName;
GO
EXEC sp_change_users_login 'Auto_Fix', 'MyDomain\warehouse';
GO
September 15, 2011 at 11:23 am
Domain permissions are best handled by working with your your system or domain admin. I still think, though, that it could be something to do with the SQL user. ...
September 15, 2011 at 11:19 am
I would try deleting the user from your dev instance of SQL Server and readding it.
EDIT: Check this out as well http://www.databasejournal.com/features/mssql/article.php/3739386/Policy-based-Management-in-SQL-Server-2008-150-Part-I.htm
Thanks,
Jared
September 15, 2011 at 10:49 am
Hmm... Have you checked the domain permissions for that user? Maybe this is not an SQL configurable piece.
Thanks,
Jared
September 15, 2011 at 10:43 am
I see... Maybe this will help you: http://www.karaszi.com/SQLServer/info_generate_script.asp
Thanks,
Jared
September 15, 2011 at 10:28 am
Viewing 15 posts - 2,551 through 2,565 (of 2,647 total)