DataBase - SQL Server Sort Order for Business Portal
Asked By L
29-Sep-08 03:40 PM
Hi all,
Our existing SQL Server database for GP uses a Binary sort order. We are
trying to install Business Portal (using Windows Share Point Services) but
the the install instructions says it can only be installed on SQL Server with
sort order 52 (Dictionary Order, Case Insensitive). If we create a new SQL
Server instance using sort order 52 for Business Portal, are there any issues
we may run into in the future regarding data exchange with GP?
Thank you.
LR
SQL Express
(1)
SQL Server
(1)
Database
(1)
Windows
(1)
DOCI
(1)
calle replied...
You can either create a new SQL Server instance using DOCI or you can let the
system install SQL Express which will automatically use DOCI (dictionary
order case insensitive).
I'm working with a client today doing a BP install and we went with the
latter approach due to their small needs. The SQL Server instance stores the
content. Unless you're going to have a lot of content, excluding the data
people are going to BP to view, you could probably do just fine with SQL
Express.
--
Charles Allen, MVP
L replied...
Could there be any conflict between the 2 instances down the road. Are you
saying BP will communicate well with GP, even when GP SQL server sort order
is Binary?
Thank you.
LR
calle replied...
Nope
--
Charles Allen, MVP
SQL query slow DataBase Hi In the code below I found that it takes 1.3 seconds to load to split it up or cancel the query? And can I read this faster? string sql = EquipmentID(Equipment) + StartDate.ToOADate().ToString(FloatFormat, myCulture) + EndDate.ToOADate().ToString(FloatFormat, myCulture); sql + = " group by event_id, name"; _Log("Calc thread #2"); OleDbCommand com = new OleDbCommand(sql, con); _Log("Calc thread #3"); From #2 to #3 it takes 1.3 seconds. Remaing less that 0.1 second. So the query is what slows it down. Access Discussions SQL Server (1) Linson Unlike Albert D. Kallal (1) MySQL (1) Windows Server 2003 (1) Visual Studio (1) SharePoint (1) NHibernate (1) Microsoft SQL Server (1) Hi
Using Mysql or SQL server as backend to Access front end DataBase Have a client having problems with a fairly complex Access system which is split into end. Using access 2003 / mdb format with Access 2007 software. We are surmising that recent server problems or connectivity problems may be to blame. If we converted to MySQL or SQL server as the back end, would that eliminate the potential for Database corruption that can occur with Access Jet databases when you lose connectivity, when someone shuts down their PC with the database active, etc? If so am I correct that you connect via ODBC rather than using
Roger Jennings on Access / Sharepoint DataBase http: / / www.quepublishing.com / articles / article.aspx?p = 1606238 I was very dismayed reading this article, is it makes it pretty clear that in-house hosting of your Sharepoint server with Access Services to support browser-based Access apps is something only large companies will 2010 does not really save them money (because of the 64-bit requirements of Sharepoint Server 2010, it could vastly increase those costs for organizations with legacy hardware). The features of email hosted by someone else, so it is not a paradigmatic change. Having your flagship database applications hosted outside your local LAN seems to me to be a big leap, and http: / / www.dfenton.com / contact via website only http: / / www.dfenton.com / DFA / Access Discussions SQL Express (1) SQL Server (1) MySQL (1) Exchange Server (1) Windows Server (1) SharePoint (1) David W. Fenton (1
Cannot link to SQL server DataBase Can any of you guys help? I am new to using SQL Server. I have a database that I wish to upsize from Access to put the back end on a server, and use Access as a front-end. However, I am stuck at the very first stage - I cannot link Access to the SQL server. I am using SQL Server Management Studio on a single computer for development purposes
Aaron Kempf's MCITP DBA proof DataBase https: / / mcp.microsoft.com / authenticate / validatemcp.aspx transcript: 944364 AccessCode: helloworld Access Discussions SQL Server 2008 R2 (1) SQL Server 2008 (1) SQL Server 2005 (1) Microsoft SQL Server Reporting Services (1) Regards Larry Linson Microsoft Office Access (1) Bing Microsoft SQL Server