information about how you use ‘Get help with ESFA services’. We use this information to make the
website work as well as possible and improve government services.
You have accepted all cookies. You can change your cookie settings at any
This is a new service – your feedback will help us to improve it.
Created 03 February 2021 09:38
We are currently experiencing issues connecting to a SQL database in FIS. We are using the out the box connection string but when we test the connecting we get unable to connect to the SQL database. Is there any advice anyone can give us on getting this working
FIS version : 1.1.13
No one has replied to this post.
Been having a lot of fun with this myself recently!
What version of SQL have you got? the "Data Source=(local);" bit of the string only works if you've got a "proper" SQL server instance running on your PC. I know in the past, where people are running SQL Express (ie the free version!), updating the string to Data Source=[[PC NAME]]\SQLEXPRESS; has worked (you can find your PC NAME by going Control Panel > System & Security > System), but definitely keen to hear anyone else's advice!!!
03 February 2021 09:55
We are using SQL express, just tried that new string you supplied and its all working thanks for your help :)
03 February 2021 10:34
I am writing this here for my own benefit for when I forget in six month's time.
If you're definitely without SQL, and are therefore having problems with PDSAT as well, here are the steps:
This worked for me at least!!!
03 February 2021 11:14
Similar headaches for me the past 2 weeks trying to get this set up on multiple machines.
I was using the Developer version of SQL 19 which FIS was fine with when i changed from (Local) to "Machinename\DatabaseInstanceName" but PDSAT just wouldn't play ball no matter what i did.
the key in the end was to install the 2019 localDB from the link that PDSAT suggests and ensure i restarted the machine after the SQL install so that the SQL instance actually booted up and was visible to PDSAT when the application launched.
I thne just replaced the connection string with (localdb)\MSSQLLocalDB as suggested and it all worked.
the bit that really stumped me was that (localdb)\MSSQLLocalDB wasn't visible in SQL management studio (SSMS or in the Windows Services so it didn't actually look like anything had installed, but connecting directly to (localdb)\MSSQLLocalDB in SSMS allowed me to see the data that PDSAT was using.
Hope that helps,
03 February 2021 12:53
Thanks Ben! Every little helps I think? [starts humming "you are not alone"]
03 February 2021 15:09
a bit late to the party but you can also have the sql connection to point to any server that has sql server installed, providing you have access to that server. SQL server doesn't have to be a local installation on your pc. Our goes direct onto our data warehouse server and all our reports run from there without having to extract data from the fis into another db.
25 February 2021 16:21
Slightly different question, but can you change the database name for the SQL server. I use to be able to specify my own name for the database, but now it seems fixed to ILR2021
26 February 2021 09:45
Hi Simon, I have enquired to the developers about this. I too used to specify the database name, having to deal with 3 ukprns, and now it is fixed and so undoes everything that i had set up this year. Currently waiting for a response
26 February 2021 11:10
Response from the SLD team.
You CAN override the database name, the change we’ve made is to support basic connectivity options that a significant number of users struggled with.
We will add a change in to make the ‘change the database name’ simpler by adding back into the new database configuration dialog screen.
In the meantime please do the following:
26 February 2021 16:28
Thank you Rhys,
That's really Helpful.
26 February 2021 16:31
So just received a new computer and setting up the PDSAT. The above worked on my previous computer but it's no longer working on the new one. Trying to work out what's going wrong.
Have installed SQL server 2019 Local DB other programs are able to connect to the server so I know it's running. However PDSAT is not able to make a connection as per step 6 in Steveh's excellent unofficial PDSAT guide. Anyone have any tips?
11 August 2021 11:57
So just started working. Not sure where I'd gone wrong, I uninstalled all SQL server packages. Then installed
Sql server express basic non developer
Then the SQL server 2019 Localdb linked to in the PDSAT and it came to life with a green tick.
Not sure what step I missed.
11 August 2021 12:21
Just because I'm about to send this thread to someone, worth pointing out that, since they updated FIS, you only have to put the server name in the box, not all the other stuff
21 September 2021 08:51