What Are You Doing Right Now
-
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
I was told to go away and what not,... but been tracking a trend with one of the DB servers,.. The F: drive is currently 61GB of the 68GB drive. Just three files are taking up 99.8% of the drive.
Trying to recover space so it can run better.
I don't follow.
specify - it's a DB server - .... for a client,... the 68GB F: drive is currently maxed out by three files (.ldf) are using 61GB of that disk.
-
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
I was told to go away and what not,... but been tracking a trend with one of the DB servers,.. The F: drive is currently 61GB of the 68GB drive. Just three files are taking up 99.8% of the drive.
Trying to recover space so it can run better.
I don't follow.
specify - it's a DB server - .... for a client,... the 68GB F: drive is currently just three files (.ldf) are using 61GB of that disk.
They need a bigger space for that DB!
-
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
I was told to go away and what not,... but been tracking a trend with one of the DB servers,.. The F: drive is currently 61GB of the 68GB drive. Just three files are taking up 99.8% of the drive.
Trying to recover space so it can run better.
I don't follow.
specify - it's a DB server - .... for a client,... the 68GB F: drive is currently just three files (.ldf) are using 61GB of that disk.
They need a bigger space for that DB!
Yea,.. we know. It requires a new server build. But I have gotten the DB(s) down sized in the past, just not seemingly working today.
-
@scottalanmiller said in What Are You Doing Right Now:
How do people find this stuff so confusing?
https://community.spiceworks.com/topic/2010950-server-2016-licensing-vms
he clearly didn't know that Hyper-V was/is it's own thing. Sounds like he doesn't know what a hypervisor is (only half way through the post).
-
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
I was told to go away and what not,... but been tracking a trend with one of the DB servers,.. The F: drive is currently 61GB of the 68GB drive. Just three files are taking up 99.8% of the drive.
Trying to recover space so it can run better.
I don't follow.
specify - it's a DB server - .... for a client,... the 68GB F: drive is currently just three files (.ldf) are using 61GB of that disk.
They need a bigger space for that DB!
Yea,.. we know. It requires a new server build. But I have gotten the DB(s) down sized in the past, just not seemingly working today.
why do they need a new server build? just put more storage in the server and expand.
Yeah I know it's more complex than that, but ya know where I'm going. -
@Dashrender said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
I was told to go away and what not,... but been tracking a trend with one of the DB servers,.. The F: drive is currently 61GB of the 68GB drive. Just three files are taking up 99.8% of the drive.
Trying to recover space so it can run better.
I don't follow.
specify - it's a DB server - .... for a client,... the 68GB F: drive is currently just three files (.ldf) are using 61GB of that disk.
They need a bigger space for that DB!
Yea,.. we know. It requires a new server build. But I have gotten the DB(s) down sized in the past, just not seemingly working today.
why do they need a new server build? just put more storage in the server and expand.
Yeah I know it's more complex than that, but ya know where I'm going.It's an OLD - dying box. There is no adding more storage. There is only (best practice) replace.
-
@gjacobse said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
I was told to go away and what not,... but been tracking a trend with one of the DB servers,.. The F: drive is currently 61GB of the 68GB drive. Just three files are taking up 99.8% of the drive.
Trying to recover space so it can run better.
I don't follow.
specify - it's a DB server - .... for a client,... the 68GB F: drive is currently just three files (.ldf) are using 61GB of that disk.
They need a bigger space for that DB!
Yea,.. we know. It requires a new server build. But I have gotten the DB(s) down sized in the past, just not seemingly working today.
why do they need a new server build? just put more storage in the server and expand.
Yeah I know it's more complex than that, but ya know where I'm going.It's an OLD - dying box. There is no adding more storage. There is only (best practice) replace.
They do not want to replace anything just bandaid it all the time. But they pay their bills and pay way too much to keep having us bandaid.
-
@Minion-Queen said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
I was told to go away and what not,... but been tracking a trend with one of the DB servers,.. The F: drive is currently 61GB of the 68GB drive. Just three files are taking up 99.8% of the drive.
Trying to recover space so it can run better.
I don't follow.
specify - it's a DB server - .... for a client,... the 68GB F: drive is currently just three files (.ldf) are using 61GB of that disk.
They need a bigger space for that DB!
Yea,.. we know. It requires a new server build. But I have gotten the DB(s) down sized in the past, just not seemingly working today.
why do they need a new server build? just put more storage in the server and expand.
Yeah I know it's more complex than that, but ya know where I'm going.It's an OLD - dying box. There is no adding more storage. There is only (best practice) replace.
They do not want to replace anything just bandaid it all the time. But they pay their bills and pay way too much to keep having us bandaid.
If they only want bandaids, and they pay a lot, then they pay too much to NOT bandaid, I suppose.
-
@scottalanmiller said in What Are You Doing Right Now:
@Minion-Queen said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
I was told to go away and what not,... but been tracking a trend with one of the DB servers,.. The F: drive is currently 61GB of the 68GB drive. Just three files are taking up 99.8% of the drive.
Trying to recover space so it can run better.
I don't follow.
specify - it's a DB server - .... for a client,... the 68GB F: drive is currently just three files (.ldf) are using 61GB of that disk.
They need a bigger space for that DB!
Yea,.. we know. It requires a new server build. But I have gotten the DB(s) down sized in the past, just not seemingly working today.
why do they need a new server build? just put more storage in the server and expand.
Yeah I know it's more complex than that, but ya know where I'm going.It's an OLD - dying box. There is no adding more storage. There is only (best practice) replace.
They do not want to replace anything just bandaid it all the time. But they pay their bills and pay way too much to keep having us bandaid.
If they only want bandaids, and they pay a lot, then they pay too much to NOT bandaid, I suppose.
Sad but true.
-
Checking this out with a grain of salt if course:
http://nerdvittles.com/?p=22598 -
@jt1001001 said in What Are You Doing Right Now:
Checking this out with a grain of salt if course:
http://nerdvittles.com/?p=22598That guy is a 3CX salesman.
-
@gjacobse said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
I was told to go away and what not,... but been tracking a trend with one of the DB servers,.. The F: drive is currently 61GB of the 68GB drive. Just three files are taking up 99.8% of the drive.
Trying to recover space so it can run better.
I don't follow.
specify - it's a DB server - .... for a client,... the 68GB F: drive is currently just three files (.ldf) are using 61GB of that disk.
They need a bigger space for that DB!
Yea,.. we know. It requires a new server build. But I have gotten the DB(s) down sized in the past, just not seemingly working today.
why do they need a new server build? just put more storage in the server and expand.
Yeah I know it's more complex than that, but ya know where I'm going.It's an OLD - dying box. There is no adding more storage. There is only (best practice) replace.
FINALLY -
Been on this box for nearly five hours. Three DBs have the status set to FULL rather than Simple. changing to Simple and Shrinking the DB took the drive from 10MB free to 25GB free - and that was just
*ONE*DB.Some back ground -
Server 2003 running MS SQL 2005... Need I say more?
ETA: Three DBs now changed and shrunk... went from the 10MB free... to 61GB Free... what is that,... 89.7% of the drive????
-
@gjacobse said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
I was told to go away and what not,... but been tracking a trend with one of the DB servers,.. The F: drive is currently 61GB of the 68GB drive. Just three files are taking up 99.8% of the drive.
Trying to recover space so it can run better.
I don't follow.
specify - it's a DB server - .... for a client,... the 68GB F: drive is currently just three files (.ldf) are using 61GB of that disk.
They need a bigger space for that DB!
Yea,.. we know. It requires a new server build. But I have gotten the DB(s) down sized in the past, just not seemingly working today.
why do they need a new server build? just put more storage in the server and expand.
Yeah I know it's more complex than that, but ya know where I'm going.It's an OLD - dying box. There is no adding more storage. There is only (best practice) replace.
FINALLY -
Been on this box for nearly five hours. Three DBs have the status set to FULL rather than Simple. changing to Simple and Shrinking the DB took the drive from 10MB free to 25GB free - and that was just
*ONE*DB.Some back ground -
Server 2003 running MS SQL 2005... Need I say more?
Hrm, is that single bill more than the move to a real platform yet?
-
@travisdh1 said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
I was told to go away and what not,... but been tracking a trend with one of the DB servers,.. The F: drive is currently 61GB of the 68GB drive. Just three files are taking up 99.8% of the drive.
Trying to recover space so it can run better.
I don't follow.
specify - it's a DB server - .... for a client,... the 68GB F: drive is currently just three files (.ldf) are using 61GB of that disk.
They need a bigger space for that DB!
Yea,.. we know. It requires a new server build. But I have gotten the DB(s) down sized in the past, just not seemingly working today.
why do they need a new server build? just put more storage in the server and expand.
Yeah I know it's more complex than that, but ya know where I'm going.It's an OLD - dying box. There is no adding more storage. There is only (best practice) replace.
FINALLY -
Been on this box for nearly five hours. Three DBs have the status set to FULL rather than Simple. changing to Simple and Shrinking the DB took the drive from 10MB free to 25GB free - and that was just
*ONE*DB.Some back ground -
Server 2003 running MS SQL 2005... Need I say more?
Hrm, is that single bill more than the move to a real platform yet?
LOL yea,.. really. Sadly this isn't the first time I have done this. It was documented (I"m pretty certain),.. but unlocateable.
This time I will need to ensure that I keep my notes. This is a case of (at least for me) PAPER is king. couldn't find S* in the ON file.
-
@gjacobse said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
I was told to go away and what not,... but been tracking a trend with one of the DB servers,.. The F: drive is currently 61GB of the 68GB drive. Just three files are taking up 99.8% of the drive.
Trying to recover space so it can run better.
I don't follow.
specify - it's a DB server - .... for a client,... the 68GB F: drive is currently just three files (.ldf) are using 61GB of that disk.
They need a bigger space for that DB!
Yea,.. we know. It requires a new server build. But I have gotten the DB(s) down sized in the past, just not seemingly working today.
why do they need a new server build? just put more storage in the server and expand.
Yeah I know it's more complex than that, but ya know where I'm going.It's an OLD - dying box. There is no adding more storage. There is only (best practice) replace.
FINALLY -
Been on this box for nearly five hours. Three DBs have the status set to FULL rather than Simple. changing to Simple and Shrinking the DB took the drive from 10MB free to 25GB free - and that was just
*ONE*DB.Some back ground -
Server 2003 running MS SQL 2005... Need I say more?
ETA: Three DBs now changed and shrunk... went from the 10MB free... to 61GB Free... what is that,... 89.7% of the drive????
Before I forget, man, supporting that must suck.
-
@travisdh1 said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
I was told to go away and what not,... but been tracking a trend with one of the DB servers,.. The F: drive is currently 61GB of the 68GB drive. Just three files are taking up 99.8% of the drive.
Trying to recover space so it can run better.
I don't follow.
specify - it's a DB server - .... for a client,... the 68GB F: drive is currently just three files (.ldf) are using 61GB of that disk.
They need a bigger space for that DB!
Yea,.. we know. It requires a new server build. But I have gotten the DB(s) down sized in the past, just not seemingly working today.
why do they need a new server build? just put more storage in the server and expand.
Yeah I know it's more complex than that, but ya know where I'm going.It's an OLD - dying box. There is no adding more storage. There is only (best practice) replace.
FINALLY -
Been on this box for nearly five hours. Three DBs have the status set to FULL rather than Simple. changing to Simple and Shrinking the DB took the drive from 10MB free to 25GB free - and that was just
*ONE*DB.Some back ground -
Server 2003 running MS SQL 2005... Need I say more?
ETA: Three DBs now changed and shrunk... went from the 10MB free... to 61GB Free... what is that,... 89.7% of the drive????
Before I forget, man, supporting that must suck.
Meh - Until I have to shrink the DB - which I many not need to do again in SIMPLE Mode. Most of the time when I need to purge old files, I can do so with the Command line feature of SC. So - no sign on needed, and takes just a minute. This sucked more since the documentation seemed lost. so had to rebuilt the brain trust....
-
Wishing "y'all" a happy Brexit of 1776
-
@scottalanmiller said in What Are You Doing Right Now:
@jt1001001 said in What Are You Doing Right Now:
Checking this out with a grain of salt if course:
http://nerdvittles.com/?p=22598That guy is a 3CX salesman.
Ward has had huge issues with Schmooze and some of the changes they made to FreePBX functionality long before Sangoma purchased it. This bias is fairly obvious in this paragraph.
There was more than a little disappointment when PaloSanto Solutions closed up their Elastix
shop last year. The good news was that 3CX stepped in with a terrific free offer on their commercial PBX for Elastix users. And, of course, Sangoma quickly learned Spanish to tout their closed source crippleware, the FreePBX Distro. But today’s a new day, and there’s another great surprise as the discontinued Elastix 4 open source product is reincarnated as Issabel 4. Featuring a respin of CentOS 7 plus Asterisk 11 and FreePBX GPL components (only), Issabel is the first new open source project in the Asterisk community in many, many years. And what a terrific GPL platform it is.That said, don't bitch about things until you read them. This article is about Issabel, the fork of Elastix 4 that is trying to keep it going. From what I have been following, the Issabel project team is trying hard, but who knows if they can actually get solid.
Ten seconds on the NV site shows that they are also looking at Wazo. So bias against the people behind FreePBX aside, NV is more than a 3CX salesman.
-
@MattSpeller said in What Are You Doing Right Now:
Wishing "y'all" a happy Brexit of 1776
It's been good for us, at least after 1783 anyway.
-
@travisdh1 said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@gjacobse said in What Are You Doing Right Now:
I was told to go away and what not,... but been tracking a trend with one of the DB servers,.. The F: drive is currently 61GB of the 68GB drive. Just three files are taking up 99.8% of the drive.
Trying to recover space so it can run better.
I don't follow.
specify - it's a DB server - .... for a client,... the 68GB F: drive is currently just three files (.ldf) are using 61GB of that disk.
They need a bigger space for that DB!
Yea,.. we know. It requires a new server build. But I have gotten the DB(s) down sized in the past, just not seemingly working today.
why do they need a new server build? just put more storage in the server and expand.
Yeah I know it's more complex than that, but ya know where I'm going.It's an OLD - dying box. There is no adding more storage. There is only (best practice) replace.
FINALLY -
Been on this box for nearly five hours. Three DBs have the status set to FULL rather than Simple. changing to Simple and Shrinking the DB took the drive from 10MB free to 25GB free - and that was just
*ONE*DB.Some back ground -
Server 2003 running MS SQL 2005... Need I say more?
ETA: Three DBs now changed and shrunk... went from the 10MB free... to 61GB Free... what is that,... 89.7% of the drive????
Before I forget, man, supporting that must suck.
Yes it does.
