Reputation
423
Top tag
Next privilege 500 Rep.
Access review queues
Badges
1 6 16
Newest
 Caucus
Impact
~48k people reached

  • 0 posts edited
  • 3 helpful flags
  • 18 votes cast
Jul
27
awarded  Caucus
Jul
24
awarded  Notable Question
Jul
10
awarded  Popular Question
Jun
30
awarded  Popular Question
Jun
23
awarded  Notable Question
Apr
14
revised Grant Windows logins to read a secondary database of log shipping?
added 65 characters in body
Apr
14
awarded  Yearling
Apr
14
asked Grant Windows logins to read a secondary database of log shipping?
Mar
24
accepted Delayed transactional replication setup?
Mar
24
asked Delayed transactional replication setup?
Mar
3
accepted Database which was set up for logshipping is dropped
Mar
3
comment Database which was set up for logshipping is dropped
There are two jobs: LSAlert_ServerName and LSBackup_DBName. Is it safe manually remove both if there is no logshipping set on the server? Or LSAlert_Server should be kept if there are other logshipping on the server?
Mar
3
comment Database which was set up for logshipping is dropped
Thanks. It seems a couple of jobs were created in the SQL Agent. Should these jobs be removed manually? Or anything else need to be done for removing these jobs?
Mar
2
asked Database which was set up for logshipping is dropped
Feb
24
awarded  Curious
Feb
23
revised Is it good to save tempdb and log files in one drive?
deleted 1 character in body
Feb
23
asked Is it good to save tempdb and log files in one drive?
Feb
2
comment Why the simple insert into query allocated a lot of tempdb?
Actually it used hash join. I guess the tempdb allocation was required by previous SQL in the session. (There were multiple SQL statements in the query window)
Feb
1
comment Why the simple insert into query allocated a lot of tempdb?
@SeanGallardy Yes, it uses merge join. However, considering the small size of the table, why it uses so many tempdb? What's the unit of tempdb_allocations btw?
Feb
1
asked Why the simple insert into query allocated a lot of tempdb?