I have a previously developed project that I am working on now. The project uses SubSonic 2.1 as ORM and it has been working fine since we decided to move to a newer server. The new server has SQL Server 2008 SP1 and now SubSonic is not behaving as usual.
I debugged the case and found that SubSonic is now generating ANSISQL queries instead of SQL Server friendly ones. I found a solution with 2.2 (customizing IsSqlServer2008 method) but I can't migrate to SubSonic 2.2 because project is really big and has lots of lots of SubSonic queries.
How can I make SubSonic 2.1 to work with SQL Server 2008 SP1?
Thanks
Tell it that you using SQL Server 2005?
2005/2008 are close enough in the sense that 7.0/2000 were.
Edit: What I mean is, override whatever so SubSonic thinks you're on SQL Server 2005.
I've never used SubSonic but your question implies you can override IsSQLServer2008 so is there a IsSQLServer2005 for older versions?
Thanks for replying. I decompiled the old dll and customized the IsSql2008 method and Sql2008Generator class. Now it works like a charm.
other problem is in sql 2000, because SQL2000 notification has in version number string "2008" , subsonic try tu use 2008 query (for paging) in 2000, and of course there is big mess.
So for SQL2000, last good subsonic 2.x version is subsonic 2.1.
Related
I'm trying to determine whether DNN 2.0.4 will be compatible with SQL Server 2005 SP4. My company is upgrading their server framework and they're trying to determine (without testing obviously...) if the SQL upgrade will blow up some of their older DNN sites.
I've trolled the boards, liberally dusted with Google magic and even skimmed through the super user manual. The nearest I've been able to get to an answer is that the latest version REQUIRES SQL Server 2005 but there's no indication that it will work with the older DNN.
Anybody out there have any concrete experience I can fall back on?
Because of the large installed base and wide variety of environments, the DNN core team has focused on using very standard SQL and I think if there was any problem, your searching would have turned something up.
Also, I'm not aware of any breaking changes or features in SQL Server 2000 that were removed in SQL Server 2005.
You should be fine. If you do run into a problem it's much more likely to be with a 3rd party module rather than the core. Some 3rd party modules were much quicker to begin to use the new capabilities of SQL Server 2005 and in general are less likely to follow standards or be tested as extensively in a wide variety of environments.
I am running 2.1.2 on SQL Server 2005 without issues. I think that the same would be true of 2.0.4.
I'm starting a new project that requires me to rewrite an existing PHP application using Codeigniter framework (v1.7.2). The existing application's database is in SQL Server 2008. The application has a lot of stored procedures that I'm required to incorporate.
Does anybody have experience using Codeigniter with SQL Server? Was the experience successful? Should I used the mssql driver or the ODBC driver?
I found an older codeigniter forum here but the information is a bit dated.
http://codeigniter.com/forums/viewthread/91918/P15/
Use Doctrine ORM 1.2 or 2 (its still in beta).
Maybe this can help you :
using doctrine 2 with SQL Server
or this
Doctrine 1.2 + MS SQL Server 2008
I have a SQL Server CE database I am developing with and would like to downgrade the version so that 2005 Management Studio will open it. Currently, I have to use VS 2010 to open it, but it is a real pain to use that way.
I know I could install the 2008 version of SSMS, but the machine I use has serious problems with all installs. There is something messed up and I don't want to reimage the machine. So 2008 is not an option.
The only way I have found is to get a tool to convert the tables into raw sql. Then use this sql against a empty DB created in a earlier CE version.
One my clients has a system written in Delphi 3 and the database is Paradox. My job is to convert it to use SQL Server 2008. How can I make it connect to SQL 2008?
This is pretty old stuff, I know. I appreciate the help.
Thanks
At the very least BDE should be able connect using ODBC and choosing the SQL 2008 Driver in ODBC. I haven't tried, but I doubt that the BDE SQL driver will connect to SQL 2008, and I doubt anybody will develop a BDE driver for 2k8.
Do you intend on moving from Delphi 3? If so, then SDAC (SQL Server Direct Access Components) from Devart would be worth looking at. They support SQL Server 2008 but unfortunately require Delphi 5 or above. They use OLE DB and any Windows machine with 2000 or above will have the drivers installed (which is part of Microsoft Data Access Components - MDAC).
You can use ADO without using Ado Components, by importing ActiveX Data Objects Library, but this will require more work.
Why not upgrade the project to Delphi 2007 as a stepping stone towards the future? There have been many improvements and bug fixes to the language since Delphi 3 that you could easily take care of. The pain of migration might be much easier than dealing with issues which have been already addressed and corrected in the latest versions of the compiler.
You can try one of the Free Components from Torry.net to connect to the SQL server using ADO.
Check TaoADODataSet and Free ADO Dataset in the page http://www.torry.net/pages.php?id=569. These components have Delphi 3 support.
How to use SQLSERVER SMO in C++(CPP) to list all the servers availabel and find databases installed using VS2003/VS2005 IDE.
And i need some clarification in
1)Does Vs2003 Have support for SQLSMO??
2)Is any additional files(reference) needed to work with SMO in VS2003? if yes what r those?
Thanks in Advance...
SMO (SQL Server Management Objects) was released with SQL Server 2005, and requires .NET 2.0 at least. VS 2003 only supports .NET 1.x.
In .NET 1.x, you'll have to revert to SQL-DMO - a COM based set of components for managing SQL Server database objects.
Marc