In order to use Teradata with .NET, do I need to do a full install of the drivers on the web server or do I just need Teradata.Client.Provider.dll and the Teradata.Net.Security.Tdgss.dll?
I found this out by trial. The Teradata driver does not reference any unmanaged pieces so it can be xcopy deployed to the bin directory on your web server.
I created a blog post on all of this:
http://wewillrulethegalaxytogether.blogspot.com/2013/12/how-to-use-teradata-with-net.html
Related
tried looking at other examples on this and am a bit confused. I have 2 web servers that are load balanced and a sql server box (sql 2012). my cube is created on the sql server box (i see it in management studio). when i try to access via my asp.net page i receive the above error.
now, i see the msolap110.dll in C:\Program Files (x86)\Microsoft Analysis Services\AS OLEDB\110 on the sql box. do i need to do something permission wise with the dll or something? do i need to install analysis services on the web server? is there a specific port or something (doubtful as sql is running fine).
connection string is as follows:
"Provider=msolap;Data Source=;Initial Catalog=AutoOLAPAW;Cube Name=SampleCube;"
going to try to force to use MSOLAP.5 but waiting on a republish from our security/deployment group.
this all works fine in dev but my (more secured/stripped down) prod/qa is where i'm seeing the issue. using iis7 on both.
If you are using ADOMD.NET then either set CopyLocal=True on that reference on your ASP.NET source code so Microsoft.AnalysisServices.AdomdClient is deployed with the web app... Or install SQL_AS_ADOMD.msi from:
https://www.microsoft.com/en-us/download/details.aspx?id=49999
If you are using OLEDB then install SQL_AS_OLEDB.msi from that same link.
If you don’t want the SQL2012 version but want the latest then install from here and use Provider=MSOLAP in the connection string (instead of a number like MSOLAP.5).
i Have a Asp website that uses MySql database, i want to publish it on my own PC for testing ,
is that possible? and do i need to combine some references with it , or what? and do i need to modify the web.config file?
There are two pieces of software required to run you application.
You need a web server that's able to serve ASP pages. Either install the full IIS, or if it's only for your own testing you can go with IIS Express (included in e.g. WebMatrix).
You need to install a MySql server to run the database. If the MySql drivers are not included in the deploy package of the site, you will need to install those separately as well.
I'm just learning orchard CMS, and have some questions:
How do I setup development environment for the team? should I use source code of orchard itself (I don't want that) or is there a way to use Orchard in compiled state?
I would prefer each developer to have its own local copy of DB, won't it make troubles for the team when they get sources and need to go in admin mode and manually execute updates on modules?
For development you should definitely set up full source enlistment. Using the compiled, deployment package (as can be downloaded from Codeplex or via WebMatrix) will drive you in lots of problems.
Orchard can run on either "normal" SQL Server or SQL Server Compact (single-file) databases.
What do you mean by a "local copy of the DB"? Each developer can test his instance using local SQL Server CE database - it's how I usually do that when working on custom modules.
If you have some preconfigured database you'd want your developers to use (because eg. it contains some sample data, themes setup and such) - each developer can copy the database from the server to his own, local SQL Server CE-based database. Migration can be easily done from Visual Studio, SSMS or WebMatrix.
How can I interact with a .mdf or.ldf file? When I say interact, I mean view/edit fields, records on the desktop.
Its inside a websites App_Data folder.
These are SQL Server files. MDF is the data file and LDF is the log file.
Basically, I think your web site is using SQL Server for it's data storage, and the database is stored in that APP_DATA folder.
Usually SQL Server installations come with Management Studio or Enterprise Manager (called Client Tools) unless the administrator chose not to install it on that machine.
Look under START / Programs / Microsoft SQL Server 2000/2005/2008. Then look for Enterprise Manager or SQL Server Management Studio.
In the ServerName, just put a period or dot, and use Windows Authentication to connect. If that does not work, you will need a username and password to connect to the database. You should be able to find either in the configuration files of the web project, or the website code.
If the Tools are not installed, then you will need the installation CD / DVD to install the client tools.
Alternately, you can install Tools (only Tools, you don't need the database engine) from SQL Express Edition from http://www.microsoft.com/express/sql/default.aspx?wa=wsignin1.0 on a different machine and access the database from there.
To "interact" with an mdf file, you need to attach the database to an MS SQL Server.
After located the mdf file you can use follwing stored procedures:
sp_attach_db
ex:
EXEC sp_attach_db
#dbname = N'MyDatabase',
#filename1 = N'D:\DataFiles\MyDatabase_Data.mdf',
#filename2 = N'E:\LogFiles\MyDatabase_Log.ldf';
Wehn DB is attached you can connect with your connection string and do classical operations on database.
You can detach your DB with sp_detach_db
ex:
EXEC sp_detach_db
#dbname = N'MyDatabase';
MSDN sample : http://msdn.microsoft.com/fr-fr/library/ms179877.aspx
Use linq2sql to access the mdf.
There's an example in an answer here
I have well developed an ASP.NET website with SQL Server 2000. How can I drop it on a server?
You might find these resources helpful:
ASP.NET Web Site Project Deployment Overview
Deploying a Database by Using the Database Publishing Wizard
How to: Deploy a Database With a Web Application Project
Depends on a number of things (e.g. if you have direct access to the server(s)). I tend to export my database structure as a SQL script and execute that against the production database. I then "publish" the site using VS and copy it across to a virtual directory on the web server.
If I am passing the application to a customer, I tend to use WiX or a VS deployment project to wrap the application up in an installer.
You can use SQL Server Publisher (free) wizard for moving database from development machine to the server. Or you can use SQL Server database schema synchronization tool by Red-gate.com
And SitePubisher for deploying files over FTP (and VPN)
There are many ways to do this.
Read this - http://www.beansoftware.com/ASP.NET-Tutorials/Deploy-ASP.NET.aspx