I'm going to be starting a web application this week. I have quite a bit of experience with Access Databases, and I've also used MySQL (back in my PHP days, thank GOD for ASP.NET).
The server we use to host our websites allows us to use SQL Server databases, so I want to move in that direction, but I'm not really sure where to start.
If I download MSDE, and start a database with it on a site I will be developing locally (on my XP box), will it be difficult for me to transfer the database (or layout of the database) to a production server running SQL Server. I know they're basically the same database, but I'm just afraid to start with an MSDE database and then get the site nearly complete, and then not know how to transfer it to a SQL Server DB.
I'm particularly interested to know if the majority of the database creation will be done through queries (similar to MySQL) because I figure if it is, then I can use the same queries to create the database on both the local and production server.
I just want to make sure that downloading MSDE will be a step in the right direction.
Perhaps links or tutorials or some information on things to watch out for as I take on this process would be so greatly appreciated.
I need to design an asp.net application w/ and MSDE backend database that will be deployed at 50 different location (unrelated to each other). The application's deployment package needs to be downloaded from a web site on the internet. The end user locations do not have SQL2000 or MSDE...some have access.
I want to know if my deployment package can include the MSDE software? Or, can anyone offer ideas on the EASIEST way for these small offices to get MSDE installed on each of their servers so that my ASP.NET applications will connect to via ado.net.
I have traditionally done web app and client server programming and am have been playing around with a new tool (Win forms) app that I eventually want to distribute to other developers and a couple of business people in our organization. I have done apps in the past that all connect to a central server for data access. The I'm working on now will have an individual DB per user and should be available locally for a desktop version of the software.
I am looking for more resources on things to consider when deploying an app with either MSDE or SQL 2005 Express. More specifically, items like long term maintenance of the db once it's installed with the user, etc. (DB bloat, transaction files, auto maintenance routines I may want to build in, etc)
I have seen all of the msdn docs on what you need to deploy (and how to do it), but I'm looking fro input from people that have deployed it and any significant pitfalls they have run into with that sort of deployment.
Any links or book references would be appreciated, thank you,
We are looking for a software program that will allow us to test our SQL server. We are looking for the most thorough tool that is available. I was asked to post a message, so I do not have too many details.
I currently have Apache, MySQL and php running on my local machine to enable me to test php code on localhost
I've been asked by a colleague if I'll work on an SQL 2000 database they're having trouble with. They said they will provide Visual.net, SQL 2000 and any other software I need.
I'm completely in the dark on this, but have some starting questions:
To test my code, will I need to set up a sever on localhost?
Will I need other software than Visual.net and SQL 2000? I'm using DW MX for my web stuff.
Whre can I find a basic introduction to ASP / SQL 2000 in the form of a tutorial?
How fast does this combination run? The database has 25,000 rows and 6 columns. What would be a reasonal expect time for a result?
What do you recommend for stress-testing the performance of key stored procedures (they have been identified) for our application? The parameters can be programatically selected, for example: Select 'exec my_proc @id = ' + Cast(id As varchar) From myTable Where foo = 'bar' I have the Support Tools Available For Stress Testing & Performance Analysis (http://www.microsoft.com/downloads/details.aspx?FamilyId=5691AB53-893A-4AAF-B4A6-9A8BB9669A8B&displaylang=en) from Microsoft's site and they are pretty good.
Recommendations appreciated, and thanks in advance!
I Run All checks for Validation cluster.I get Error On Disk Lists And Validation failed.With This error : Failed to prepare storage for testing on node "server name" The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation.
I have a server with several linked servers. Before I execute sql against any of these linked servers I want to check to make sure the connection is active.
I created a small stored procedure that takes the server name. I am trying to get it to run a simple select statement. If the select statement runs without errors (meaning the linked server is active) I want to return a value for success. If the select statement fails I want to return a value for a failure.
The problem is that I am having trouble with the error. When I shut down the linked server and run the select statement I get the following error returned:
Server: Msg 11, Level 16, State 1, Line 1 General network error. Check your network documentation.
The stored procedure I have only returns this message and does not send the return value that I set. How do I get my procedure to return a failure value instead of the following error above? Is there a better way for me to check for this type of error?
Hi Group, I'm trying to test an ASP application in 'isolation' and seem to be having problems with connecting to the Server. The setup is EXACTLY like the production environment except for the fact that I am using the Beta version of SQL.
The error refers to SQL Server not existing. I get this error also if I try to open the Query Analyzer without FIRST starting the Services via the Service Manager - so I think it is probably something wrong with the Beta Installation rather than using the BETA version as a back-end.
I've tried using the Computer name as the Server to connect to as well as 127.0.0.0 - neither seem to want to connect.
I can connect manually and see the Database objects. I've even connected, left the connection open and tried running the application again. I still get the same error.
Has anyone experienced this before? i.e not being able to connect to a BETA version of SQL to test an ASP application locally.
Hi, I'm new to the whole MS SQL server thing, have been using Access in past developments via the development platform in Dreamweaver.
Now I'm making the leap to MS SQL and still want to use Dreamweaver to handle some of the development aspects, does anyone know how or what i would need to do to have a direct connection with the server in dreamweaver?
I've setup an ODBC connection with my hosting providers already.
What is the syntax to telnet a database?I triedtelnet <hostname> 1433 - but get this error:telnet ws1234 1433Connecting To ws1234...Could not open connection to the host, on port 1433: Connect failedMy computer name is ws1234.comHow do I test a connection to a sql server database instance?Thanks,VVvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvWW
Our database is in Sql Server 2005 Mode 80 at the moment and we need to switch it to Mode 90. We need a lilst of all incompatibilities that exist.
Essentially, we need a list similar to what the Upgrade Advisor provides for 2000 databases. The only problem is our DB is already in 2005 mode 80. Switching to mode 90 is easy but does not identify all potential problems for us.
Is there a tool that is similar to the Upgrade Advisor that we can run on 2005 Mode 80 databases?
Are there any differences between the Developer Addition and Enterprise Addition of 64 Bit SQL Server 05 that would prevent me from testing full capabilities of my production Enterprise Addition in a QA environment utilizing Developer Addition? Any known restrictions on number of DB connections, memory, CPUs etc??
I have some C# code that is pulling data from a database where a majority of the values being retrieved are NULL , yet their initial column data types are both string and int, which means that I have to temporarily store these NULL's in int and string data types in C#. Later on in my code I have to test against these values, and was wondering if I am doing it correctly with the following code.
The following statement the variable or_team_home_id is of a string data type, but may have had a NULL value assigned to it from the database if (!or_team_home_id.Equals(DBNull.Value)) {}
The following statement the variable or_manager_id is of a int data type, but also may have a NULL value assigned to it from the database. if (!Convert.IsDBNull(or_manager_id)){}
Are these the correct way to test against NULL values retrieved from teh database and that are stored in their respective data types.
Recently, we have migrated our database from 32bit to 64bit. So far the application is working fine.
But I want to confirm that by any tool or automated process.
Is there any way or tool to check that the migrated data is correct and also to check if migrated database objects will work fine in 64 bit environment.
We are using Sql Server 2008 R2. We are planning to move to 2014 either through in-place o side-by-side. Mostly side-by-side.
Here first we want to test that 2014 and availability groups. First we are doing in dev box to test. Also we need asynchronous replica because just we need to use that as reporting server.
We want to take work load. For the dev boxes, the applications doesn't connect. Then in that case what the people will do.
If We take database backup from prod to that dev and run some queries in the loop and run the trace for some time and do either in-place migration or side-by-side migration and use the same back to restore and doing the running the same queries and compare this trace to previous trace will work?
Because of a performance problem, somebody has given me a script which came from a SSRS report.
The code as supplied does not work when multivalued parameters are used.
Testing/tuning/building in SSMS is far superiour than in SSRS. So that's why I like to use SSRS for building the code/script/sql-statement. Offcourse parameters have to be set correctly. (That is no problem). Splitting of the multivalued parameter is not a problem either.
I have what seems a simple requirement. We want to import the contents of a SQL Server 2005 Reporting Services report into a SQL Server 2005 database, in order to perform some checks on reports displayed to users. Is there an easy way to achieve this? XML would seem appropriate, but I can't find a step-by-step guide on how to achieve this. Any pointers/suggestions would be appreciated.
I am doing SQL Server deployment of multiple SSIS projects. 2 of the projects have dtsx files that are named the same. Is there anyway to deploy to SQL Server to put these in different projects so that they dont conflict?
I have integrated Share Point server 2007 with Reports Server to publish the reports on share point site. I did all steps involved for integration
I have share point server, reports server and database server on three different machines configured and when I am trying to publish the reports from my local Dev box, setting the below project properties, target datasource folder: http://vstsvr:168/sites/wsL/ReportsLibrary/ target report folder: http://vstsvr:168/sites/wsL/ReportsLibrary/ target Server url: http://vstsvr:168/sites/wsL/
I am getting the following error:
TITLE: Microsoft Report Designer ------------------------------ A connection could not be made to the report server http://vstsvr:168/sites/wsL/. ------------------------------ ADDITIONAL INFORMATION: Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'. The request failed with the error message: -- <HTML dir="ltr"> <HEAD><meta name="GENERATOR" content="Microsoft SharePoint" /><meta name="progid" content="SharePoint.WebPartPage.Document" /><meta HTTP-EQUIV="Content-Type" content="text/html; charset=utf-8" /><meta HTTP-EQUIV="Expires" content="0" /><meta name="ROBOTS" content="NOHTMLINDEX" /><title>
<table width=100% border=0 class="ms-titleareaframe" cellpadding=0> <TR> <TD valign=top width="100%" style="padding-top: 10px" class="ms-descriptiontext"> <span id="ctl00_PlaceHolderMain_LabelMessage">The file you are attempting to save or retrieve has been blocked from this Web site by the server administrators.</span> <P><span class="ms-descriptiontext"> <span id="ctl00_PlaceHolderMain_helptopic_troubleshooting"><A Title="Troubleshoot issues with Windows SharePoint Services. - Opens in new window" HREF="javascript:HelpWindowKey('troubleshooting')">Troubleshoot issues with Windows SharePoint Services.</A></span>
Hello,I am currently creating a web app that I am creating using the Visual Web Developer Express IDE to create. I was planning on using a SQL Server Express database for the database backend. My problem is this...The web server i will deploying the app too does not have SQL Server, or Server Exress installed...can I still use the Server Express Database? Excuse my ignorance on this subject as I have is the passed used MS Access databases (my employer has never wanted to shell out the $$$ for SQL Server on our web server). Thanks in Advance for your help.-Dan
I've written an app in C# with ASP.NET in VS. I can connect from my development computer (laptop - XP) to MY server (Win 2003) running MS SQL just fine.
However, when I try to deploy it on the server that it is supposed to run on, I can't connect. I can connect through the network to the SQL server, but I just can't do it with the app. This tells me that my connection string must be wrong... Of course, suggestions would be great...
The SQL server (7.0) is on Windows NT. The app is on a windows 2000 server, and yes, .NET Framework is installed. The Windows NT server is the web server, and the 2000 has been set up as www2. I can see the app from the net, but when I try to log in (requiring connection to the SQL server to verify user and pword), no go.
These are my connection strings, please correct me if I'm wrong...
I've also tried them without the trusted connection, and with the server name... Same result (or lack thereof).
There's two connection strings, because one is used for the select statements for the public, and the other has all permissions for the back-end. I know it's redundant, but it's just one more safety feature I built in for the paranoid 'client'.
I have also tried to run the SQL server off of the 2000 box, but there's an error with the MMC... Does anyone know how to fix that, if it's a better solution???
Our workstations (XP SP2) and development servers (2003 R2) are all 32-bit. Our Staging and Production SQL Servers are 64-bit (2003 R2 x64). We have some VB SQLCLR assemblies we've developed.
My question is: Do we have to do anything special when deploying a CLR Assembly to a 64-bit box when it has been compiled on a 32-bit box? Are there any advantages to setting the Target CPU from "AnyCPU" to "x64"? Documentation and testing seems to indicate that the assembly will run in 64-bit mode if compiled to "AnyCPU".
Will it run "better" in 64-bit mode with the "x64" Target CPU type?
I have a multiple report server deployment, and we removed one of the servers from the farm, however the name still appears in the list on the initialize screen in report server configurator.
We removed reporting services from this box, but the name still appears in the list.
I am currently deploying my website. I cannot establish a link with the SQL sever express database. I followed the instructions of my web host (covered in this thread): http://forums.asp.net/thread/1698700.aspx and finally I received the currently unresolved error: "An attempt to attach an auto-named database for file d:hostingmembersharpeeuksite1App_Dataaspnetdb.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share." I told my webhost I have followed their instructions and they came back with the answer: "I would suggest you to upgrade the db's to use mssql 2005. This is because, sql express is built for development environment. When you are in development environment, you are accessing everything with administrator permission. However, in live hosting environment (when there are differnet kind of permission restrictions), sql express often failed on attaching database. Any kind of change to the database would require re-attaching database. Personally, I do not feel sql express is ready for the live hosting environment. We can try to fix the attaching problem for you, however, even if we do it for free for you, you might encounter attaching db problem the next time you make any kind of update to the database schema. " Is this correct? Is SQL server Express really unsuitable for deployment? I am using webhost4life.com - Does someone know a webhost that can host SQL server Express reliably? (that would seem a lot cheaper than upgrading to mssql 2005) Thanks for any advice
My site is hosted by Fasthosts(.co.uk), which means I cannot put an MS SQL database on my site: they don't support that sort of thing. I have to pay for a seperate SQL database on a seperate server (also hosted by fasthosts). They have given me an IP, a server name, a database name, login and password. They tell me that the server require SQL authentication. I have managed to contect to the database using MS VWD 2005 through the database explorer. I cannot however make changes to the database. I have therefore downloaded SQL Server Management Express. This is where I am stuck. I can't seem to get the software to find my database. One thing I have tried is i've set up a database on my system and then run replication. When I do this I get stuch at to the "enter the name of the computer running IIS" part of the wizard, I've tried entering in the IP of the server and the ip of my website. I have also tried connecting to the database direct (not using replication) but this fails when it tries, despite all the combinations of IP, server name and database name I try! Any ideas? Regards, Howard
I would like to know how I can deploy Microsoft SQL 2000 Server Personal edition using SMS 2003 Sp2.
When I map a drive and I execute my batch file it install SQL 2000 correctly but when I try to deploy SQL 2000 server personal edition using SMS 2003, It said that I deployed successfully sql 2000 server but when I look into my client computer, it didn't install SQL so this is the problem I have.
This is probably a dumb question. But if I embed a SQL Server Express database into my project and then attempt to deploy it via ClickOnce, will I be able to access that database using the SQL Server Management Studio Express CTP if it is installed on the same machine as the client that my app would be installed?
I can not completely understand how to deploy sse with my application
To some degree I understand the explaning in Mikes Documentation
Things I don't get:
1)Do I not check the prerequisite server express because when I did and run the setup.exe that I build the thing that happens is that the sql package gets unpacked over and over along with a little message that it's taking a little longer then expected. I gues this is the fallpit where the actual setup.exe for sse is nothing being done with hence the wrapper.
A quote from Mikes document "If the VS Bootstrapper isn't flexible enough for you then". Well, I don't know what I'am doing wrong but it doesn't work at all. I had no problem with the other prerequisites (Framework, installer)
Back to the first question: if so do I manually add the SQLEXP.EXE (downloaded from the internet) or is it the sqlexpr32.exe in the same folder as the setup.exe for the application?
2) How is the wrapper invoked? I don't see that mentioned. I thought when you start the application itself, but that hardly seems logical.
Please anyone, give me some clear directions or additional expanatory
hello, i got this error when i tried to build my project prior to deployment. S.O.S. Error 1 System.ApplicationException: Could not copy file "D:Documents and SettingsMy DocumentsVisual Studio 2005ProjectsSSISSolutionSSISSolutionPackageConfig.dtsConfig" to the deployment utility output directory "D:Documents and SettingsMy DocumentsVisual Studio 2005ProjectsSSISSolutionSSISSolutioninDeployment". ---> System.IO.IOException: The file 'D:Documents and SettingsMy DocumentsVisual Studio 2005ProjectsSSISSolutionSSISSolutioninDeploymentPackageConfig.dtsConfig' already exists. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite) at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.CopyFiles(ICollection fileNames, String outputPath) --- End of inner exception stack trace --- at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.CopyFiles(ICollection fileNames, String outputPath) at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.CreateDeploymentUtility(IOutputWindow outputWindow) 0 0
