I've been working with sql server 2008 exclusively through the visual studio interface since I've started coding. I'm trying to get at my database in the SSMS, and I connect, but my database is visible, but not expandable in the object explorer.. I see an object count of 0 in the object explorer details. In VS, I have a full database heirarchy to work with, dozens of tables, sprocs, functions. The connection string points to the same location. Any ideas? I have RTFM to no avail. :)
Turns out my database was awaiting recovery... this was fixed by running the following:
ALTER DATABASE Market SET OFFLINE
GO
ALTER DATABASE Market SET ONLINE
GO
Related
I am able to import records into Filemaker using actualtech trial drives, but do not know how to update PostgreSQL database when making changes in Filemaker.
Ideally I would like Filemaker to remain as a front-end and PostgreSQL be the backend in the event they would like to move away from Filemaker.
Is there a real-time dynamic updating with ODBC connections?
Some troubleshooting and biting the bullet... but I bought Open Source Driver from Actual Tech and it seems to be working.
Not very intuitive but I learned I can import records from postgreSQL using the "Open Source Driver" and I can then setup a relationship with the "ESS Driver" (File / Manage Database / Relationships ) to use postgreSQL as a backend; meaning updating real-time.
I would like to make a tutorial in the future because it was a few hours of trial and error.
We have a project that is being worked on currently by 5 developers and could get more at any time. The developers are located at different places in the US. Our back end is Code First Entity Framework based on a SQL Server database.
Some of the developers have SQL Server Express and some have full blown SQL Server. We need a way to have the solution everyone works on but each developer needs to have his own connection string to the data so they can connect to their individual instances. We cant use localhost because express versions have named instances of SQLEXPRESS.
We could just change the connection string when we grab the code form Git but then every time we sync we will have conflicts to merge so that would be a pain.
Has anyone run into this?
A very simple solution would be to have everyone use SQL Server Express or SQL Server Developer Edition. You can install both side-by-side, so that should not be an issue. Especially since SQL Express is free...
Another option is to define a SQL Server Connection Alias on each client with a predefined name. Then add the alias to your .config. That way the SQL Client will resolve to the right database and you can define one static value in your .config.
The 3rd solution is to add a configsource="connectionstrings.config" and create these files on the local workspace, but don't check them in. You can add a connectionstrings.template.config and check that in to provide a starting point. These files don't need to be part of the solution.
The 4th option is to store the connectionstring in a .Settings file, set it to user and use the standard configuration API to store the connectionstring in the application settings folder of the users profile. You'll need to pass the connectionstring to the constructor of the Context class.
I have been working with Microsoft SQL Server since 6.5 along with other database like Oracle, MySQL and SQLite. I equally appreciate or hate all these DBMS for some point or the other.
On our forthcoming project, we are considering Postgres in the back-end. I have already started playing with it, pretty interesting for me.
I have always heard good comments on Postgres database, but I don't like the admin studio at all. While creating new a table, I hate the way of creating columns on pgAdmin by having to click add button again and again.
Are there any "Studios" for Postgres database that provide
more organized table creation process (spreadsheet like)
graphical view designer
What's wrong with plain SQL? Writing plain SQL goes much faster than click-wait-click-wait-type-click-wait-ok-wait. You could use any tool for this, pgAdmin as well.
Open Office Base can also connect with PostgreSQL, works like MS Access. And talking about MS Access, MS Access can also connect to PostgreSQL to create tables, views, etc.
See this official list of Administration/Development tools.
EMS SQL Manager seems to be a good option.
for the graphical view of SQL queries
maybe SQLeo can Help
I have an app the runs at the store level extracting data out of a POS system. This app asks the POS system for data which in return produces some .DBF files. The app loads the DBFs in memory and saves it to SQL Server 2008 Express at the store level. This happens at 3 different stores.
I have been looking into the Microsoft Sync Framework, but have not come across any good examples of how to sync tables in one direction only, from each of the stores into a single database at the corporate level.
The data at each one of the stores is being managed by the app(delete, update, insert).
Does anyone know a good article, that I could read about synchronizing SQL data?
Thank you.
Try the following link
http://www.codeproject.com/KB/database/DTS_SQLExpress.aspx
I'm looking for advices and suggestions on how to synchronise data between two databases.
The first database is a SQL Server 2008 Express that run on disconnected laptops (no network or internet access). The second database (main) is a VFP 9.0 that run on a server.
When the user connect their laptop on the network, I want the synchronisation process to go through.
Other than the different database engines, I have the following items to take into account:
The tables don't necessary have the same structure
The primary keys are not the same (GUID in the SQL Server and often a combination of character fields in VFP)
Synchronisation of the tables must be done in a certain order to respect the parent-child relationships
On some insert on the SQL Server side, a new primary key must be generated and synchronised in the VFP table
A bunch of validations must be made and some feedback from the user are sometimes needed
Not all records need to be synchronised
Some records on the SQL Server need to be deleted after the syncronisation
Need to take into account deleted records from both side
Minimal modifications need to be done on the VFP database
There are probably other points I'm forgotting now, but I think you get the idea of the challenge I face. My guess right now are that I will need to build a custom synchronisation module, but I want your input before I go on in case I overlooked some options and to get some tips on how to approach this.
I looked rapidly at Microsoft Sync Framework, but with all the restrictions I have and the fact that there is no VFP client already built (AFAIK), I don't think it will be of great help.
Thanks in advance for your feedback.
Update: The laptop application is a C# WinForm application and is using SQL Server 2008 Express.
The complexity of the situation and requirements leads me to believe you need to write a Visual FoxPro application. Visual FoxPro connects to SQL Server 2008 data easily. The complexity of the code is matching the requirements and identifying the data that needs to be synched, not the syntax. Visual FoxPro strength is in the data manipulation language and the ability to connect to almost any data source (native DBFs, ODBC, ADO, and XML).
SQL Server can read VFP 9 data via the VFP 9 OLE DB driver. You could write T-SQL stored procedures to get to the VFP data. Not sure how it would recognize the laptop being connected to the network though.
Another approach is to use SQL Server XML Diffgrams. I am not an expert by any stretch of the imagination on this approach, but it would be something you can research.
Since my expertise is with Visual FoxPro I would find it way easier to go the other way though, but that is just me. You have to go with the skillset of the resources you have for the project.
VFP reads and writes SQL Server data via a connection (DSN, ConnectionString) and any technique involving SQL Passthrough (SQLConnect(), SQLExec() and SQLDisconnect()), CursorAdapters, Remote Views, or a combination of the three.
A Visual FoxPro program can also recognize Windows Events like connecting to a network. The application could be installed on each laptop and running to recognize the Windows Event. Once the event is raised the application can attempt to connect to the SQL Server database (possible it is connecting to a network without the SQL Server available or a different network).
Once connected it runs the logic to check and synchronize the databases.
Sounds like you don't have a lot of control over the application writing to the VFP 9 data on the laptop. If you do have control over the application writing to the VFP 9 database you might consider changing the app to write to a SQL Server Express instance on the laptop and then you can use SQL Server replication to manage the synchronization. Not a trivial task though and SQL Server replication, while getting better with each release, does cause hair loss in DBAs. Definitely a lot of work going this route.
Rick Schummer
Visual FoxPro MVP
I would encourage you to take another look at MS sync framework. We have a situation where we want to synchronize occasionally connected C# clients apps with our Java/Oracle backend. You can use the sync framework providers for the C# client and implement your own custom subclass of KnowledgeSyncProvider for the backend. This will get you half-way there, and show you a good pattern to apply for the rest.