Reputation
647
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
1 6 18
Impact
~85k people reached

Feb
25
awarded  Notable Question
Feb
20
awarded  Popular Question
Jan
28
comment How do I configure SQL Server 2012 so that it can restore and see files in my user account?
I'm not sure it clears the confusion... If you're logged on via WA, your SQL Server account needs the permissions to restore (as far as SQL Server is concerned), but the SQL Server service account needs the read permissions on the file system to open the .bak file (which it generally won't have if it's in your user directory, unless explicitly granted).
Nov
18
awarded  Notable Question
Nov
17
awarded  Yearling
Oct
15
awarded  Popular Question
Sep
30
awarded  Explainer
Jul
4
awarded  Popular Question
Jul
2
awarded  Curious
Jun
25
answered Return a default value in group by if selected column is null
Jun
25
asked Efficiently joining two irregular series representing changes
Feb
3
awarded  Informed
Jan
17
awarded  Popular Question
Nov
28
asked Limiting PostgreSQL logging
Jul
26
accepted PostgreSQL strategies to deal with disk filling up
Jul
26
comment PostgreSQL strategies to deal with disk filling up
Interesting, pg_freespace doesn't quite return as much as VACUUM FULL is able to reclaim aferwards, but I guess it's close enough. Thank you.
Jul
25
comment PostgreSQL strategies to deal with disk filling up
Sorry, I meant I'd like to know how much space belonging to the tables (and used on disk) is actually unused and re-usable. As far as I can tell, pg_database_size returns the size on disk.
Jul
25
awarded  Popular Question
Jul
25
comment PostgreSQL strategies to deal with disk filling up
This sounds like a good approach. Do you know if there would be a way to do this based on the space available on the partition? I don't know whether there is a way to know the actual space used (by the data that's not deleted) or what could potentially be available. (I could certainly put the pg_xlog on a different partition too.)
Jul
23
asked PostgreSQL strategies to deal with disk filling up