Viewing 15 posts - 6,331 through 6,345 (of 7,185 total)
Jaybee
I think you need to add 'OurDomain\OurNTLocalGroup' as a login before you can make it the owner of the database. I'm guessing that what happened is that the login used...
August 21, 2007 at 5:42 am
Please will you post DDL for your log table so that we can see, for example, what data type your timecreated column is. It's difficult to see why you're using...
August 21, 2007 at 4:57 am
Jaybee
Try removing OurNTLocalGroup as a user from the database. Then execute sp_changedbowner 'OurDomain\OurNTLocalGroup' and that should change the owner for you.
John
August 21, 2007 at 4:52 am
Subu
Plenty of things it could be. Search this site for "tempdb size increasing" and you'll find a lot of them.
John
August 21, 2007 at 1:43 am
Mark
Check your CONCAT_NULL_YIELDS_NULL setting. The default is ON, so if one of the values you are concatenating is null, you will end up with a null whatever the other strings...
August 20, 2007 at 6:16 am
Sudheesh
Please will you provide some DDL for your tables and let us know what you have tried so far.
Thanks
John
Edit:- Looks like Ken has spared you the trouble!
August 20, 2007 at 6:09 am
But now you're using @tg-2 without having declared it. Look up CREATE PROCEDURE in Books Online. Your code will look something like this:
CREATE PROCEDURE dbo.MyProc @tg-2 varchar(10)
AS
.......
GO
John
August 10, 2007 at 9:17 am
Ezhilan
Since you are dropping the table at the end, is there any reason why you can't just use a temporary table (#MyTable)?
John
August 10, 2007 at 4:17 am
August 10, 2007 at 4:15 am
As far as I know, that isn't allowed. Something like this should work:
DECLARE
@name SYSNAME
SELECT
@name
August 10, 2007 at 2:40 am
Truncate a table, or truncate the transaction log? There's information about both of these in Books Online.
John
August 9, 2007 at 9:12 am
Does your stored procedure have parameters, and if so, are you passing different parameters in the second time? It's always helpful if you post your code, by the way.
John
August 9, 2007 at 7:52 am
August 9, 2007 at 6:53 am
Chris
I think the answer is "just because". sa has fixed permissions and therefore you can't add it to or remove it from fixed server roles, hence the error message.
John
August 9, 2007 at 6:22 am
Chris
Yes, sa can perform any task that a member of security admin can (and more). Mind you if your thrid party product requires the sa account, then it's probably time...
August 9, 2007 at 4:16 am
Viewing 15 posts - 6,331 through 6,345 (of 7,185 total)