Now it may be that they had money to flaunt that they could burn in the past, burnt it all, and are now living with the consequences of throwing that money away. But that's a little different. They still felt that throwing money away was worth it at the time. Today, sure, maybe they've run out of money, or many they just say that to justify decisions, but at the last time that they were making IT spending decisions....

@JaredBusch said in Mental Process - Migrating from Wasp Mobile Asset to Snipe IT: The hard part of anything like this is the manual labor to organize shit. If it was my call, I would spin up a clean new system and using a report form the old system only import the valid assets. Manually do the f***ed up assets the right way. and then set a migration date. Kill change access to the old system and use it only for reporting purposes. Yeah, that does make the most sense. And the manual labor is the worst part. It always is.

at "200 character width" I started thinking about the COBOL class I took in college.

I got it restored to a new db,.. but i did have to change the file name.

@DustinB3403 said in Microsoft SQL Express 2005 - Complete Database Backup - help: @coliver said in Microsoft SQL Express 2005 - Complete Database Backup - help: @DustinB3403 said in Microsoft SQL Express 2005 - Complete Database Backup - help: And I have a feeling the software is crap... that or I'm just doing this wrong.. You might be doing it wrong. The basic/free version is very limited, from what we saw. What are you having issues with? Oh sorry I'm not trialing that backup software yet. I'm using the built in tools from the application vendor to try and restore a .BAK into a clean installation. Oh, I see.

@aaronstuder said in Changing SQL SPN: You missed blacking out some hostnames Damn VNC!