I have found this project on Codeplex.
http://www.codeplex.com/ProjNET
I need to integrate this code with Sql Server 2008, and found a similar project on the Web
http://sqlspatialtools.codeplex.com/
The second one can be bound to Sql Server. What do i need to do, to "bind" the first one, the same way as the first?
EDIT using code like create assembly and functions in Sql Server, Sql Spatial tools is bound to SQL.
I'm not sure i made myself clear, but if i take the same approach, all i need is to register the first one, the same way as the second?
http://sqlspatialtools.codeplex.com/sourcecontrol/changeset/view/23749?projectName=sqlspatialtools#255008 (check SQL Scripts->register.sql)
Any light on this matter?
Thank you everyone.
Studying the .sql file on Sql Spatial tools em and another friend was able to find the correct pathway that we needed.
We builded a function on ProjNet API, and then in Sql Server 2008 we did this:
create assembly ProjNET 'pathToFile'
go
create function ourFunction(signature) returns geography
as external projnet.ourNamespace.Function
Thanks for the attention everyone.
G.
Related
I have created a Database in SQL Server using MS SQL Management studio.
I'm looking for a simple GUI tool to easily search in the database or add new data to the database.
for example, if my database stores links for pictures - each picture has some tables like location, objects, animals, lighting etc.
I want to be able to search the database, so i can choose of a box list for each table instead of Querying through the SQL.
i understand this can be done with Sharepoint and MS Access, but i recon it's too complicated.
any thoughts and ideas?
thnx.
Try using EMS SQL Manager for SQL Server - it has free Lite version which ones limitations are acceptable.
Also you may try DevArt's dbForge Studio for SQL Server - this product's progress is very impressive. It's one of the best solutions for managing SQL Server.
I'm starting to learn database, and I will work with SQLce. Is there some type of library that can assist in creating the proper SQL statements for creating tables etc? (Not for query of the database, as I plan to use LINQ). I'm not thinking an MS library, but some amateur project maybe..
You want to download SQL Server Management Studio Express. The SSMS tools let you connect to SQL CE as well as the full blown SQL Server databases, and best of all it's free. You can create your tables via the GUI, and then instead of saving the table, you could have it show you the SQL script instead and learn that way. Everything you do in the GUI executes T-SQL behind the scenes and you have the option of saving all that SQL and running it yourself.
See this stackoverflow question here too for some more details.
I've written my website using ASP.NET MVC and SQL Server (used a SQL Server instance which ran locally on my machine).
I'm about to upload my site to a hosting provider. However, his DB works under MySQL. I don't care about the data already in the DB itself. It's mostly mock data and a few tables which I don't mind rewriting. But how do I go about the transition from SQL Server to MySQL? How does this influence my queries inside my code? is it the same code syntax? Will I have to recreate the table definitions? In my project I used LINQ to SQL.
Am I forced to look for a host with SQL Server capabilities (i.e. licenses)? (I hope not...)
Thanks!
You may be able to transition smoothly, but I greatly doubt this will be the case.
The differences are many and whether you could depends on what features you used when developing.
If you kept to one of the standards, you may be in luck.
See a comparison sheet on wikipedia.
In regards to the Linq aspect of your question - you should be able to use a Linq provider for MySql instead of MSSql without a problem.
Here is a link to one: http://code2code.net/DB_Linq/
If you do decide to go with the MySql hosting, I suggest you test all aspects of you application to ensure they are working as expected.
LINQ to SQL works with MS SQL Server only...so if you want to keep using it, you need to find a host with a MSSQL database.
Well met! I'm missing something about VS2010... I want to create a solution that let's me use the visual query designer to build queries against an SQL server, as I can when I right click the server in Server Explorer and select New Query. However, I can't seem to save this sort of query.
If I go into Solution Explorer, I can create a new TSQL query, but I cannot use the visual designer. ???
So, what am I missing? I'm sure there is some reasonable and over-arching design paradigm that is just completely eluding me as to why the Solution Explorer and Server Explorer would be so disintegrated that I could not create a query in the one and save it as part of a solution.
Thank you for your help!
It's my understanding that SQL 2008 is built in to VS2010. Therefore you shouldn't have to use SQL Server MS.
I have MS Access 2007 Databases and VBA modules associated with it.
I Now want to upgrade my project so as to use Sql Server 2005 and Vb.net using visual studio.net.
Can any one suggest Complete details on the transfer without much hassle or data loss.?
Thanks In Advance
Per RBarry's answer...the data migration to SQL Server is easy using the SQL Server Migration wizard. Then you will have a working microsoft access application (probably but maybe it will require polishing and tweaking).
To convert the front end (ui) to vb.net there might be a converter but even if there is one you would likely have to do a lot of it manually anyway. So you treat the access version like a prototype and you start building your app in vb.net by hand.
Seth
Start with the Ms-Access SSMA site: http://www.microsoft.com/sqlserver/2005/en/us/migration-access.aspx
I am not aware of a migration guide specifically for Access -> SqlSever, however, there is a very extensive Oracle -> SqlServer Migration Guide that you could easily cherry-pick for a project plan.
I use SQL Server to import data from Access databases. Be aware that it won't import your keys or relationships- you'll need to recreate those.
Your VBA code is specific to Access. You'll need to rewrite it in VB.NET.
The Access queries are probably going to cause you the most trouble. Simple ones can be converted with the Upsizing Wizard, but the more complex ones will have to be rewritten in SQL.
Also note SQL Server objects follow different naming conventions. An Access table is typically prefixed with tbl, SQL tables typically aren't named with a prefix.