Viewing 15 posts - 976 through 990 (of 1,366 total)
The reason is because u dont have permission...
April 28, 2010 at 11:16 pm
Please check whether its .ldf or .mdf file thats growing ...
Tat might be ldf and u can shrink that...
April 28, 2010 at 7:15 am
Thanks Ninja,
So TRUNCATE and DELETE are almost same then why its like TRUNCATE can be done by using an ALTER permission where as DELETE cannot and need specific permission?
April 28, 2010 at 6:33 am
Thanks Pradeep..
Can you please let me know why like this?? I wonder why Truncate remove all data which cannot be rolled back with just an ALTER PERMISSION
TIA
April 28, 2010 at 5:33 am
Thanks alot grant & Eric for that informative and quick reply..
April 27, 2010 at 10:56 pm
Hi Sudhakara,
Try creating a db mail so that you will automatically get answer for ur question
April 20, 2010 at 11:49 pm
account_idmail account id
Servernameserver type (SMTP,MAPI)
servernameMail Server Name
portPort
usernameUser name
credential_id
use_default_credentials0 for no and 1 for yes
enable_ssl1 for no and 1 for yes(secure socket layer)
flags
last_mod_datetimemodified date
last_mod_usermodified by user
April 20, 2010 at 5:24 am
many reasons..
1. any job inserting bulk data into that database.
2.some other offline operation on related tables.
3.backup database job start by that time.
4.maintenance plans
5.tempdb full
6.cpu,memory bottleneck
7.too many indexes
8.excessive normalization
April 20, 2010 at 4:52 am
created a user having only read permission in SOURCE SERVER.
select security tab under linked server properties in TARGET SERVER and use that user in BE MADE USING THIS...
April 16, 2010 at 5:32 am
A database can become suspect for several reasons. Possible causes include denial of access to a database resource by the operating system, and the unavailability or corruption of one or...
April 16, 2010 at 4:58 am
Viewing 15 posts - 976 through 990 (of 1,366 total)