I would like to create integration tests for a program that will be connected to a SQL Server in production.
But I would like the unit tests to be shippable and loadable without the need for a running SQL Server...
I am willing to write a stub to adapt to the alternating SQLServer / "Light SQL for tests"
I would like to keep the existing T-SQL queries as they are. Not change a single dot in them.
Would you kindly suggest an option ?
Unless you use advanced T-SQL features, SQL CE ought to be enough.
Related
just a question about Neo4j and graph databases: Is there something similar like SQL Server Management Studio from Microsoft?
Background information: I have to compare SQL vs graph databases for study. For the practical section I need to implement a friend structure (of social networks) for sql and (I chosen) Neo4j. I just want to compare the speed of both dbs (performance test). So if I execute a query I need the execution time - and I know SQL Server Management Studio does this.
Or has someone any other solution/idea for comparison? :)
Thanks.
It depends on what you are testing. If you are testing Cypher execution speed (which is not optimized for performance yet), then you get timings with the result set. Otherwise, you could implement an unmanaged extension that measures queries as they come in and get executed, see http://docs.neo4j.org/chunked/milestone/server-unmanaged-extensions.html .
Working on adding unit testing around database code on a Java legacy project. Some of SQL (Oracle) contains analytics functions .. (i.e. parition over syntax). Is there any in memory SQL DB options out there (preferably open-source) that support these functions?
Any other solutions? I would prefer not to hit the real database (even if I rollback the data).
Postgre SQL support window & analytic function.
check the docs here
you need to think if it's smart to test the data on a different platform though.
If you are using Oracle, I would just spin up a local copy of Oracle XE because it is free. This ensures that your test environment mirrors your production environment. While it may be wise to use something like HyperSonic it is not a true representation of your production environment and as such some issues may be missed that could have been caught in test.
I have a database that I build a lot of views on.
I currently write these views in straight SQL using SQL Server Management Studio.
My question is "are there other tools that developers commonly use to build SQL queries and views" ?
I'm really looking for an IDE for SQL.
Do these count?
http://www.ssmstoolspack.com/
I'm in the process of learning SQL, and I need a way of verifying that my SQL queries are valid (i.e. no syntax errors). I also would like to check what results they yield on a test database of my choosing and structure.
I'm using embedded firebird in my C# .NET application, so I don't really have any tools to work with. Anyone have any tips? Perhaps there are SQL administrators/query IDEs out there that work with Firebird?
You can use IBExpert personal or DatabaseWorkbench Lite
check also this and this
We have a massive amount of stored procedures to convert from sql-server 2000 to oracle 10g. Does anyone know of any tool that would achieve this?
We used Oracle SQL developer for this but it seems like it is creating extra cursors for each IF/ELSE condition that was on sql server side.
Has anyone successfully used a tool that would do this?
Sorry, no answer, and you have my sympathies. I've been through this before and it was all manual. We ended up making distinct migration & test plan tasks for it.
Oracle will use cursors in places that look odd for people used to SQL server. I am not aware of any (simple) way around this.
There seem to be a number of companies out there now offering services or tools to help: This Google search shows a bunch.
Don't forget to plan for functional equivalence testing. Datatype differences may cause issues, and your application development tool(s) may interact differently with Oracle than they do with SQL server. I did this conversion a number of years ago for a PowerBuilder application, and a lot more of that needed updating than we expected.