I was wondering if anybody had any good ideas for managing a Securities database? Currently the db is an Access db and there is talk of migrating it to a SQL server. However, does anybody know of a good front-end UI that would help non-technical people query the SQL server that holds Securities information?
If there are already UI forms in Access, you can keep them. Move the data to SQL-Server and have the Access database link to the tables in SQL-Server. Of course, you could also build a web-based interface, a desktop app, etc...
Related
I use a SQL Server 2017 database to perform ad-hoc data analytics activities to support my team. In order to source data from various databases, I either mount a backup on my environment (if the target DB holding the data I’m after is also SQL Server) or use linked servers to establish a direct connection (where I need data from Oracle or iSeries).
More recently though I’m coming across SaaS based systems and was wondering if there’s any way I can establish a direct connection between my database and the SaaS database? I’m not sure whether SSIS packages will do the trick. Any pointers would be gratefully appreciated as I’m struggling to get the right, scalable solution for this problem!
Data integration with SaaS solutions is a mixed bag. You have to discover on a case-by-case basis what integration or data export functionality each SaaS application has. Few will allow any kind of direct database access, but you might find an ETL tool that has pretty broad connectivity.
In Azure you can look at Logic Apps Connectors, and Power Query Connectors. Or products like Boomi. Which have connectors for many popular SaaS Applications.
I have been tasked with migrating an existing MS Access database to SQL Server 2012. It appears that using the SSMA for Access is the best choice for completing this migration. I have done some review of the migration assistant and it seems to be pretty straight forward. The kicker is that this client wants to use the existing Access forms with the data that has been migrated to SQL Server. So once the migration is complete, I need to point all of the current Access forms, queries, and reports at the new data source. I am not sure of the best way to accomplish this. I see that there is an option to 'link tables' when using the migration assistant but I am guessing there is more work to do to get the entire access front end working with the SQL backend. I don't have much Access experience so any help or advice on the best way to accomplish this would be much appreciated. Thanks!
The SSMA tool can also redirect its table definitions (the entries under the 'Tables' tab in the database window) so that they reference the migrated data in SQL Server. Forms, queries and reports all use these table definitions, so you may well find that most things work as expected immediately after migration. However, there are some aspects that do not move successfully, and you are likely to hit some of these if there is much VBA code in your application.
I am looking into developing a new user registration system for my company. In the past we have made use of ASP.net for all web development.
Due to the huge charge associated with this I am looking at moving towards a more open source alternative. The issue at the moment is that the db we have is SQL Server and we have no way of changing this in the forth coming future.
Has anyone any experience of building a django application with SQL Server backend for the database?
I would most like to hear of any issues you may have faced.
Thanks
Looks like there's some decent resources out there:
http://code.google.com/p/django-mssql/
http://code.google.com/p/django-pyodbc/
https://code.djangoproject.com/wiki/DjangoOnWindowsWithIISAndSQLServer
I personally don't have experience with it, and the backporting of your models from db->code could possibly be a painful step. Also, it seems like most of these packages want to work with sqlserver 2000 or 2005, so hopefully you are not using 2008.
After reading through some articles on LightSwitch, I'm left wondering what prevents a LightSwitch user creating queries that over load the data-source, mainly SQL databases.
From my initial understanding, a LightSwitch user is not a developer or DB admin, and may little understanding of the impact a seemingly simple query can have on a multi-user database.
Does LightSwitch have built in governance, caching etc, is it safe to let the user have access to the last years sales data?
I don't believe there is anything built into LightSwitch for this, however this should be able to be handled on the DB server.
If you're running SQL Server 2008 they've got resource governance built in.
MSDN SQL 2008 Resource Governance
Specific example
I am developing a simple WPF Application that requires a database. My question is, can I use an online database to run with my application. That is, can my WPF application access an online database? If yes, then how do I do it? Will the conventional way of accessing the SQL Server work? Also, is there any free online database website available that I can use. I do not need a lot of space. Just need to store 9-10 tables, and about 15-20 stored procedures.
Take a look at "SQL AZURE". The call it Database as Service: http://msdn.microsoft.com/en-us/sqlserver/dataservices/default.aspx
Additionally you could look at Amazon SimpleDB http://aws.amazon.com/simpledb/.