The server's a stock Dell server; his roll-your-own solutions mostly popped up in software where he reinvented the wheel because ... well, just because. This is partially because he and his team were really badly managed; that dummy of a manager I complain about in here used to be the head of the team that RYO-guy was on before they ran their product into the ground. Like, all the way into the ground; we stopped selling it and it's end-of-support date is June of this year.
Good news: the upgrade went off without a hitch. Though I seem unable to upgrade the vm-hardware; there's an odd mix of restrictions about what versions of hardware the free stuff can deal with when I tried looking into it. Also, licenses for the VMware server-side stuff seem expensive and I wind up very confused as to which product(s) we'd need.
Bluuuuuh. Anybody got some tips for figuring out a DNS issue. We just got our new fiber connection at work but we're still running into issues with DNS lookup timeouts.
The server's a stock Dell server; his roll-your-own solutions mostly popped up in software where he reinvented the wheel because ... well, just because. This is partially because he and his team were really badly managed; that dummy of a manager I complain about in here used to be the head of the team that RYO-guy was on before they ran their product into the ground. Like, all the way into the ground; we stopped selling it and it's end-of-support date is June of this year.
Good news: the upgrade went off without a hitch. Though I seem unable to upgrade the vm-hardware; there's an odd mix of restrictions about what versions of hardware the free stuff can deal with when I tried looking into it. Also, licenses for the VMware server-side stuff seem expensive and I wind up very confused as to which product(s) we'd need.
Look into the vmware essentials bundle. It's a great deal and super affordable.
0
jeffinvaKooglercoming this summerRegistered Userregular
I'm on day two of six days off. I was paged last night for a pretty mundane task (replacing a BBWC module and battery) but a new-ish engineer needed some guidance, and asked separately by another engineer to spruce up some technical documentation. I haven't had time to get started on my own bullshit projects. Important stuff. I mean this Steam Machine isn't going to build itself.
Bluuuuuh. Anybody got some tips for figuring out a DNS issue. We just got our new fiber connection at work but we're still running into issues with DNS lookup timeouts.
Bluuuuuh. Anybody got some tips for figuring out a DNS issue. We just got our new fiber connection at work but we're still running into issues with DNS lookup timeouts.
With the new fiber connection, did you have to switch ISPs?
While I agree that being insensitive is an issue, so is being oversensitive.
+1
DietarySupplementStill not approved by the FDADublin, OHRegistered Userregular
edited March 2014
"Hey, you're the sernior DBA. We had you build a SQL Server for a third party application a couple weeks ago, right?"
Probably.
"Well the vendor is trying to sign in and finish the configuration, but they don't know the password to the service account."
You mean the actual Active Directory service account?
"No, it's a SQL login. Do you have the password?"
That's something you should ask them, since they asked to set them up themselves and ranted and raved when I said no the first time and suggested they stick to AD authentication.
"Can't you see the passwords?"
No.
"How about you just give the contractor sysadmin?"
Sigh.
DietarySupplement on
+8
DietarySupplementStill not approved by the FDADublin, OHRegistered Userregular
Bluuuuuh. Anybody got some tips for figuring out a DNS issue. We just got our new fiber connection at work but we're still running into issues with DNS lookup timeouts.
With the new fiber connection, did you have to switch ISPs?
Yeah, from Windstream to ATT. I always chalked it up to our shitty T1 but we're still seeing some issues. SonicWALL router, and I've tried both the DNS servers ATT supplied and Google's
0
lwt1973King of ThievesSyndicationRegistered Userregular
SQL server and RDP are not the same thing.
By interchanging them and saying you can't get in using SQL server just confuses everyone and makes a whole lot of frustrating troubleshooting.
"He's sulking in his tent like Achilles! It's the Iliad?...from Homer?! READ A BOOK!!" -Handy
Bluuuuuh. Anybody got some tips for figuring out a DNS issue. We just got our new fiber connection at work but we're still running into issues with DNS lookup timeouts.
With the new fiber connection, did you have to switch ISPs?
Yeah, from Windstream to ATT. I always chalked it up to our shitty T1 but we're still seeing some issues. SonicWALL router, and I've tried both the DNS servers ATT supplied and Google's
I was going to suggest trying Google, but you done did dat....
Can you set up a connection outside of SonicWALL to see if you are still getting the same problem? That will narrow down if it is something internal to your network or the connection going out.
While I agree that being insensitive is an issue, so is being oversensitive.
Bluuuuuh. Anybody got some tips for figuring out a DNS issue. We just got our new fiber connection at work but we're still running into issues with DNS lookup timeouts.
With the new fiber connection, did you have to switch ISPs?
Yeah, from Windstream to ATT. I always chalked it up to our shitty T1 but we're still seeing some issues. SonicWALL router, and I've tried both the DNS servers ATT supplied and Google's
I was going to suggest trying Google, but you done did dat....
Can you set up a connection outside of SonicWALL to see if you are still getting the same problem? That will narrow down if it is something internal to your network or the connection going out.
I have a hunch it's the network itself. A month or two ago one of our oldest and mostly unused servers kicked the bucket (it was mostly being used as an terminal services box) and we replaced it with a new Server 2012 box. It was given the same IP as the replaced box but I'm wondering if someone forgot to set it up DNS on it.
I inherited most of this stuff from a guy who did zero documentation. His idea of a corporate router was a Netgear with Tomato installed on it. DNS server was pointed at the router rather than the DNS servers of the new connection.
Just had to add the ATT DNS servers to it and it's working awesome now.
Bluuuuuh. Anybody got some tips for figuring out a DNS issue. We just got our new fiber connection at work but we're still running into issues with DNS lookup timeouts.
With the new fiber connection, did you have to switch ISPs?
Yeah, from Windstream to ATT. I always chalked it up to our shitty T1 but we're still seeing some issues. SonicWALL router, and I've tried both the DNS servers ATT supplied and Google's
I am not the only on with a t1 line! Do you have 6,9, or 12 megabits? I have 9! yay 9!
Maybe we should have 250 clients use this connection yes?
Bluuuuuh. Anybody got some tips for figuring out a DNS issue. We just got our new fiber connection at work but we're still running into issues with DNS lookup timeouts.
With the new fiber connection, did you have to switch ISPs?
Yeah, from Windstream to ATT. I always chalked it up to our shitty T1 but we're still seeing some issues. SonicWALL router, and I've tried both the DNS servers ATT supplied and Google's
I am not the only on with a t1 line! Do you have 6,9, or 12 megabits? I have 9! yay 9!
Maybe we should have 250 clients use this connection yes?
I've recently gotten us off T1 lines, except for one remaining satellite office that nobody else wants to provide service to.
9 megabits? What luxury, we had 2. 2. We use Remote Desktop for literally everything.
Bluuuuuh. Anybody got some tips for figuring out a DNS issue. We just got our new fiber connection at work but we're still running into issues with DNS lookup timeouts.
With the new fiber connection, did you have to switch ISPs?
Yeah, from Windstream to ATT. I always chalked it up to our shitty T1 but we're still seeing some issues. SonicWALL router, and I've tried both the DNS servers ATT supplied and Google's
I am not the only on with a t1 line! Do you have 6,9, or 12 megabits? I have 9! yay 9!
Maybe we should have 250 clients use this connection yes?
My friend texts me yesterday while I'm pooping that they lost power at his office and now their server has errors and won't boot, stuck configuring updates. I suggest a couple things, quickly google up a technet forum post about it.
Later on Live he's like "Man, that link you sent me sounds exactly like what our problem is, but since we contract our IT out to another company we don't even have the discs and stuff available to try and fix it. And my boss would probably mad if I tried it anyway. Course those are the guys that took forever to get my computer set up right so I'm not gonna be surprised if I can't get anything done in the office tomorrow."
I didn't have the heart to tell him all it took me was 2 minutes on the toilet.
Can you confirm the permissions on this database match the user/SQL details you're trying to use?
Does SQL server have ip based limitations like MySQL? I think it does, check that too.
:rotate:
support says that the copy of the database from the NT Backup is likely not going to cut it
there are no SQL backups anywhere, so we're going to have to try it anyway, but it looks like I'm in for a fun day tomorrow.
Sounds... Untrue.
So basically the app can only create a new db, read the db that already exists and is configured with whatever pointers exist in the app, or restore a SQL .bak file.
This is a decade old, btw, and I'm lucky this guy even still works at the company.
Currently copying the SQL db files to another client, who has a full version of SQL 2000 running, to make a backup to then transfer back and import
Bluuuuuh. Anybody got some tips for figuring out a DNS issue. We just got our new fiber connection at work but we're still running into issues with DNS lookup timeouts.
With the new fiber connection, did you have to switch ISPs?
Yeah, from Windstream to ATT. I always chalked it up to our shitty T1 but we're still seeing some issues. SonicWALL router, and I've tried both the DNS servers ATT supplied and Google's
I am not the only on with a t1 line! Do you have 6,9, or 12 megabits? I have 9! yay 9!
Maybe we should have 250 clients use this connection yes?
Bluuuuuh. Anybody got some tips for figuring out a DNS issue. We just got our new fiber connection at work but we're still running into issues with DNS lookup timeouts.
With the new fiber connection, did you have to switch ISPs?
Yeah, from Windstream to ATT. I always chalked it up to our shitty T1 but we're still seeing some issues. SonicWALL router, and I've tried both the DNS servers ATT supplied and Google's
I am not the only on with a t1 line! Do you have 6,9, or 12 megabits? I have 9! yay 9!
Maybe we should have 250 clients use this connection yes?
What? for a business. I have 25 at home. I honestly can't imagine that shared.
It fucking suuuuuucked. We're a manufacturing company and the office park we're in was farmland 20 years ago.
No telcos were willing to run anything out here.
Thankfully, another tenant of the office park is a construction firm. They made a deal with ATT where they'd dig the ditches and run the fiber. We happen to be along the route so our telco vendor tipped us off to it last year. It's been nearly six months from the day we signed the contract to the go-live at the end of last week.
Now that I got that DNS thing fixed it's like a goddamn miracle.
We were splitting that 3MB among about 30+ people. Then it got to be too much, so we bonded two T1s and switched the existing one over to solely handle our VoIP traffic.
Speaking of, anyone have experience with Star2Star as a voip provider? I'm running into a weird issue with'em that I'm hoping I can fix and provide our CS Department a 'digital switchboard' app they can use to route calls.
TL DRNot at all confident in his reflexive opinions of thingsRegistered Userregular
edited March 2014
So what do you do if you have a database, ostensibly created in and for SQL 2000, that will attach and complete a backup in SQL 2008, that will not attach in SQL 2000 citing 'error 602 could not find row in sysindexes'? Assume that you really, really need to be able to create a new SQL 2000 backup. The original server that it lived on is kaput.
TL DR on
0
Apothe0sisHave you ever questioned the nature of your reality?Registered Userregular
I would feed.
Alternatively, I would allow the application to create a new database. Dump the database into SQL form rather than a backup from 2008. Take the application offline, run the mega sql query that was dumped.
My friend texts me yesterday while I'm pooping that they lost power at his office and now their server has errors and won't boot, stuck configuring updates. I suggest a couple things, quickly google up a technet forum post about it.
Later on Live he's like "Man, that link you sent me sounds exactly like what our problem is, but since we contract our IT out to another company we don't even have the discs and stuff available to try and fix it. And my boss would probably mad if I tried it anyway. Course those are the guys that took forever to get my computer set up right so I'm not gonna be surprised if I can't get anything done in the office tomorrow."
I didn't have the heart to tell him all it took me was 2 minutes on the toilet.
So apparently my friend ended up having to fix the server (it was what I sent him + a UPS problem), because their IT guy couldn't fix it last night. Bear in mind my friend is a business major for whom the closest he's gotten to IT was building his own gaming PC with my help and just general user competence.
He wasn't able to tell me the full story via txt, but he promises it is one of "Comical incompetence".
So what do you do if you have a database, ostensibly created in and for SQL 2000, that will attach and complete a backup in SQL 2008, that will not attach in SQL 2000 citing 'error 602 could not find row in sysindexes'? Assume that you really, really need to be able to create a new SQL 2000 backup. The original server that it lived on is kaput.
So let me try and understand: you had a SQL Server database, created in SQL Server 2000. You then detached it and attached the database to a 2008 server, but you can't attach the database to another SQL Server 2000 server?
If the database was upgraded during the attaching process, you might be out of luck as databases can move forward but not backwards in versions. That's why it's best practice to create a backup of the database and then restore (but in your case if the server was borked, you might not have had a choice).
Is the other SQL 2000 server running the same service pack and cumulative update?
Failing that, you can script out each individual object in the database, create them, and then pump in the data via identity inserts. There's two ways to do that: either via the SSMS console or via powershell; I wrote some scripts that do that if you're interested (although you'd probably have to attach the database in 2008 on some server that supports powershell).
+2
Donovan PuppyfuckerA dagger in the dark isworth a thousand swords in the morningRegistered Userregular
A lot of people seem to be unable to grasp the fact that if you give us food, you will be bumped to the top of the line. Also if you are not a complete ass, you'll be bumped even more to the top!
IT runs on coffee and free cookies, man. At least at all the jobs I've worked it has.
One of the remote agencies was getting a lot of new employees in and was going to need them all set up, so she called ahead to Chick Fil A and got us some trays of those tiny chicken biscuit things? Delicious.
Anyway her employees were all set up quickly and with a smile.
Taking your car into a garage to get some work done? Ask the service advisor what the workshop supervisor's favourite beer is, and buy a carton of it for the boys t share on a Friday arvo.
So what do you do if you have a database, ostensibly created in and for SQL 2000, that will attach and complete a backup in SQL 2008, that will not attach in SQL 2000 citing 'error 602 could not find row in sysindexes'? Assume that you really, really need to be able to create a new SQL 2000 backup. The original server that it lived on is kaput.
So let me try and understand: you had a SQL Server database, created in SQL Server 2000. You then detached it and attached the database to a 2008 server, but you can't attach the database to another SQL Server 2000 server?
If the database was upgraded during the attaching process, you might be out of luck as databases can move forward but not backwards in versions. That's why it's best practice to create a backup of the database and then restore (but in your case if the server was borked, you might not have had a choice).
Is the other SQL 2000 server running the same service pack and cumulative update?
Failing that, you can script out each individual object in the database, create them, and then pump in the data via identity inserts. There's two ways to do that: either via the SSMS console or via powershell; I wrote some scripts that do that if you're interested (although you'd probably have to attach the database in 2008 on some server that supports powershell).
DietarySupplement is pretty much on point here. There's no easy way out of this. Backups, Backups, Backups before you fuck with production data. You said the original server was kaput, where did you get this DB copy from?
Posts
Good news: the upgrade went off without a hitch. Though I seem unable to upgrade the vm-hardware; there's an odd mix of restrictions about what versions of hardware the free stuff can deal with when I tried looking into it. Also, licenses for the VMware server-side stuff seem expensive and I wind up very confused as to which product(s) we'd need.
Look into the vmware essentials bundle. It's a great deal and super affordable.
Damn, if they would pay for my World of Warcraft subscription, I'd be much more willing to help them.
My Steam profile
3DS: 1435-3951-4785
You need to elaborate a little more than this.
Second call of the day (seconds after): BSOD
I never liked mornings to begin with... it may be an angry music day
Probably.
"Well the vendor is trying to sign in and finish the configuration, but they don't know the password to the service account."
You mean the actual Active Directory service account?
"No, it's a SQL login. Do you have the password?"
That's something you should ask them, since they asked to set them up themselves and ranted and raved when I said no the first time and suggested they stick to AD authentication.
"Can't you see the passwords?"
No.
"How about you just give the contractor sysadmin?"
Sigh.
Yeah, from Windstream to ATT. I always chalked it up to our shitty T1 but we're still seeing some issues. SonicWALL router, and I've tried both the DNS servers ATT supplied and Google's
By interchanging them and saying you can't get in using SQL server just confuses everyone and makes a whole lot of frustrating troubleshooting.
Can you set up a connection outside of SonicWALL to see if you are still getting the same problem? That will narrow down if it is something internal to your network or the connection going out.
I have a hunch it's the network itself. A month or two ago one of our oldest and mostly unused servers kicked the bucket (it was mostly being used as an terminal services box) and we replaced it with a new Server 2012 box. It was given the same IP as the replaced box but I'm wondering if someone forgot to set it up DNS on it.
I inherited most of this stuff from a guy who did zero documentation. His idea of a corporate router was a Netgear with Tomato installed on it. DNS server was pointed at the router rather than the DNS servers of the new connection.
Just had to add the ATT DNS servers to it and it's working awesome now.
I am not the only on with a t1 line! Do you have 6,9, or 12 megabits? I have 9! yay 9!
Maybe we should have 250 clients use this connection yes?
I've recently gotten us off T1 lines, except for one remaining satellite office that nobody else wants to provide service to.
9 megabits? What luxury, we had 2. 2. We use Remote Desktop for literally everything.
3
THREEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
But now we are on fiber 50/50 (but really around 30/15 during regular hours)
Later on Live he's like "Man, that link you sent me sounds exactly like what our problem is, but since we contract our IT out to another company we don't even have the discs and stuff available to try and fix it. And my boss would probably mad if I tried it anyway. Course those are the guys that took forever to get my computer set up right so I'm not gonna be surprised if I can't get anything done in the office tomorrow."
I didn't have the heart to tell him all it took me was 2 minutes on the toilet.
PSN - sumowot
So basically the app can only create a new db, read the db that already exists and is configured with whatever pointers exist in the app, or restore a SQL .bak file.
This is a decade old, btw, and I'm lucky this guy even still works at the company.
Currently copying the SQL db files to another client, who has a full version of SQL 2000 running, to make a backup to then transfer back and import
I picked a bad week to become OT-exempt
What? for a business. I have 25 at home. I honestly can't imagine that shared.
It fucking suuuuuucked. We're a manufacturing company and the office park we're in was farmland 20 years ago.
No telcos were willing to run anything out here.
Thankfully, another tenant of the office park is a construction firm. They made a deal with ATT where they'd dig the ditches and run the fiber. We happen to be along the route so our telco vendor tipped us off to it last year. It's been nearly six months from the day we signed the contract to the go-live at the end of last week.
Now that I got that DNS thing fixed it's like a goddamn miracle.
We were splitting that 3MB among about 30+ people. Then it got to be too much, so we bonded two T1s and switched the existing one over to solely handle our VoIP traffic.
Just finished setting this up today. Feeling like a real handy man now
Alternatively, I would allow the application to create a new database. Dump the database into SQL form rather than a backup from 2008. Take the application offline, run the mega sql query that was dumped.
Then I would hold onto my ass.
Well I replaced the switch in a ceiling fan.
He wasn't able to tell me the full story via txt, but he promises it is one of "Comical incompetence".
Lol. Rackspace sent me an Iron Man iPhone case for my birthday
So let me try and understand: you had a SQL Server database, created in SQL Server 2000. You then detached it and attached the database to a 2008 server, but you can't attach the database to another SQL Server 2000 server?
If the database was upgraded during the attaching process, you might be out of luck as databases can move forward but not backwards in versions. That's why it's best practice to create a backup of the database and then restore (but in your case if the server was borked, you might not have had a choice).
Is the other SQL 2000 server running the same service pack and cumulative update?
Failing that, you can script out each individual object in the database, create them, and then pump in the data via identity inserts. There's two ways to do that: either via the SSMS console or via powershell; I wrote some scripts that do that if you're interested (although you'd probably have to attach the database in 2008 on some server that supports powershell).
Taking your car into a garage to get some work done? Ask the service advisor what the workshop supervisor's favourite beer is, and buy a carton of it for the boys t share on a Friday arvo.
DietarySupplement is pretty much on point here. There's no easy way out of this. Backups, Backups, Backups before you fuck with production data. You said the original server was kaput, where did you get this DB copy from?
Incidentally, why can it only live in SQL 2000?