SQL
Every day is a school day!
Since we came back I have been trying to install a software update onto the server as a multiple-user program rather than two (rising to three) stand-alone versions.
As every attempt to install the software requires a server reboot which takes 20 minutes minimum my efforts have been restricted to weekends.
The software instructions were good, but only really intelligible if you had done this sort of thing before. Which I haven't.
I had to create a new user with very specific permissions, and get them to install the programs. It wasn't helped by the instructions referring to old versions of Server, meaning I was looking for options that have now been renamed and are accessed in a different way.
Now, after numerous attempts I have finally managed to install another SQL instance on the server, beside the other two, which means I can install the program and then work out how to move the databases from the individual computers to the server without losing the data. And making sure everyone can use the software. And making sure it is being backed up properly.
I need to sort this next week, but reading the instructions makes my brain hurt.
This is definitely not for the faint hearted.
Since we came back I have been trying to install a software update onto the server as a multiple-user program rather than two (rising to three) stand-alone versions.
As every attempt to install the software requires a server reboot which takes 20 minutes minimum my efforts have been restricted to weekends.
The software instructions were good, but only really intelligible if you had done this sort of thing before. Which I haven't.
I had to create a new user with very specific permissions, and get them to install the programs. It wasn't helped by the instructions referring to old versions of Server, meaning I was looking for options that have now been renamed and are accessed in a different way.
Now, after numerous attempts I have finally managed to install another SQL instance on the server, beside the other two, which means I can install the program and then work out how to move the databases from the individual computers to the server without losing the data. And making sure everyone can use the software. And making sure it is being backed up properly.
I need to sort this next week, but reading the instructions makes my brain hurt.
This is definitely not for the faint hearted.
5 comments:
I don't want to make your head hurt any further however using virtual machines can be useful for this kind of thing. You can install to a virtual server runs the same as a normal server however its contents are all saved as a single file on your disk ... so you can copy it, try something out, and then delete the copy if things don't work out. Or backup the whole server to a single disk.
You can run multiple virtual servers on a single physical server which can also be useful.
[Insert extremely tenuous justification for writing a pro-SNP / pro-Labour / anti-SNP / anti-Labour comment here]
The instructions are clear, you probably have multiple named instances now.....your poor machine.
SQL Server is for IT professionals, not have a go hobbyists, you'll be claiming to be an expert in SQL, TSQL and SSRS soon no doubt ;-)
That's probably the SNP's fault too.
Labour wouldn't have brought in SQL server, flat behemoth cobol files is more their style......on a central server so they can control it of course.
Anon 12:31. I have only one named instance of the new installation; something I repeatedly checked at each install failure. I have linked one workstation to the new instance, but I haven't had the time or brain space to look at migrating the existing data files to the server.
We already run SQL for a business critical piece of software, so I have a basic knowledge of how to back-up and restore the databases, and not much beyond; and I won't claim to have very much more knowledge now, beyond the basics.
The instructions were NOT clear, as the software required a download and install of the full sql package in a very precise manner to avoid install failures. I took a crash course in sql install errors via the web, and whilst not really understanding much of what they were on about, I got enough to understand why I was getting a fail message in the log files, and what to do about it.
If the IT wonks spent more time making sure their software installed in all circumstance and less on acronyms...
Here's a very useful beginners guide to SSRS whilst smug geeks might try this SSRS site in lieu of getting out more.
lol
Angus,
You've actually got further than some SQL server contractors I've and the misfortune to work with, our current guy is probably on £45ph and is useless and knows about about SQL Server as Gordon Brown knew about global economics. Are you free ? Surely labour central office won't pay you that much ;-)
How's your .NET code, try and decipherer this.
Dim MyFavouriteParty as String = "Labour"
MyFavouriteParty.Replace("La","Lie")
Well done on your million hits btw.
Post a Comment