Scenario: ISS 8.5 is on our work machines, our Microsoft SQL Server is currently down for an indeterminate amount of time, and we don't have a back-up. We can continue to develop code on localhost. Because SQL Server is down, we can't execute any data transactions. Are there any reliable resources online to, at least, test if the developed SQL syntax is correct?
Edit: I will go ahead and eat my words. I had presumed that we were not allowed to install SQL Server Express locally. That was a bad guess. After I had sent our boss the suggestion from marc_s, he gave us the go-ahead. Now we have a back-up plan. For the record, the SQL Server is now online.
You must have access to another SQL server in order to test code against a SQL server. Your only options are to install SQL server on local machines, install SQL server on a local networked computer, or use a SQL server installed at a third party host.
Related
I was wondering if the Microsoft SQL Server the Free Edition is a SQL server than i can connect to from any other PC even if i shutdown the main PC which has the SQL server installed on, or it is just a local SQL server and the PC should always be online to allow other connections to?
You can have either a server installation like the free Express edition. It can be installed on a server or any other machine (even the client machine itself). It also bring the SQLLocalDB which is a light version of the Express Edition. In all cases the computer that hosts the database needs to be available for access (in your case as mentioned turned on).
https://www.microsoft.com/en-us/download/details.aspx?id=101064
If you have the need that the database should be available without having to turn on a computer, you want to take a look at the Azure SQL database versions which are the cloud based versions of SQL Server. Depending on the needs you can pick from different flavours like the serverless tier:
https://learn.microsoft.com/en-us/azure/azure-sql/database/serverless-tier-overview?view=azuresql
i don't know where to ask this I hope sof is the right place.
I give t-sql classes to a professional school, and it's my first time. The school doesn't have any software installed but they want it to be microsoft sql server only. So the thing is, I know in oracle I can have a server installed at home and my students use a client to connect to it and each using their separete db-user, execute the tasks I ask, all is fine and dandy. With sql server from microsoft I don't even know/can't find a client version... I'm talking about 2012 version.
So... is there a client software to acess a sql server or any other similar way? Currently I enabled everything I could related to ssh and I'm trying to connect with other machine to my sql server via ssh but to no success. (I considered this another possible solution)
The thing is, I don't wan't to install 20 SQL servers on desktops... I think it doesn't make much sense since all their tasks are related to SQL sintaxe and basic rules and database normalization.
I'm sorry for my english, I'm not native.
You can use Sqlserver Manament Studio. Which is used to connect sqlserver from client or server means, in network or even though from live sqlserver too.
one thing you remember about 32-bit , 64 bit version.
http://en.wikipedia.org/wiki/SQL_Server_Management_Studio
http://msdn.microsoft.com/en-IN/library/bb934498.aspx
Follow the link that how to install SSMS.
http://blogs.msdn.com/b/bethmassi/archive/2011/02/18/step-by-step-installing-sql-server-management-studio-2008-express-after-visual-studio-2010.aspx
I am looking to create a database server that can be used to store data using a VB.net application. When I initially installed SQL Server 2005 Express edition, I believe I installed this using the LocalDB option.
As it stands my application is a simple tool which utilises the Process.Start command under certain situations, depending on user input, to launch Game Servers for use at a gaming LAN I assist in running.
I wish to progress the application by being able to update, delete and query a database created in SQL Server 2005 Express. I understand the use of connection strings etc, however I am wondering if the installation using LocalDB will mean that I cannot connect to the server to process the data I require.
Can I continue to use the LocalDB option and create a Database Server for specific use using my application or is a different installation option required?
Secondly, can someone point me in the right direction of how to create a new Server for this purpose? All of my searches so far have provided results for creating a database only, and not the server.
I have a couple questions about what you are trying to do.
First, why are you installing SQL Server 2005? It was released almost a decade ago.
I would go with 2012 express edition.
http://www.microsoft.com/en-us/download/details.aspx?id=29062
Second, install the management tools. SSMS is a nice GUI to do work in.
Third, If you are spinning up anything other than express, there are licensing costs which are quite high. 9K for standard and 25K for enterprise per socket or such.
Here are the versions and features list from microsoft.
http://technet.microsoft.com/en-us/library/ms144275.aspx
Last but not least, having the express edition on another computer is fine. However, you will have to use a network protocol such as TCP/IP instead of shared memory.
It will take longer to send Tabular Data Stream (TDS) to the other computer versus talking to memory on the same computer.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/c4f06669-41fd-42e6-b4a9-564cf04ca9f7/how-to-choose-between-shared-memory-named-pipes-tcpip-via?forum=sqlgetstarted
Good luck with your project.
You can use a local instance of SQL Server just fine, if you want to set up a separate server for some reason then you'll need either a 2nd machine on which to install SQL Server, or to spin up a virtual machine. If running Windows 8 (and barring hardware limitations) you have Hyper-V at your fingertips.
This is not a complete answer for you but may give you some things to think about.
First you might want to think about your choice of database. If you don't have a compelling reason for using 2005 you will probably at least want to move to SQL Express 2008.
Second, to answer the part about creating a server... A server is something that serves data. In a general sense a computer configured to be contacted by external machines and respond with data is a server. A web server runs a program like IIS or Apache to respond with web pages. A database server contains a database and allows connections to that database. So as long as you install the database on a computer and configure it to allow external connections, you have your database server.
In MS SQL there are several things that need to be set up to allow a database to accept external connections. One is that the SQL Server Browser service will need to be active. Another is that the database itself will need to be configured to allow external connections (SQL Authentication type probably).
Hope this helps.
Addition:
SQL Remote Connection Configuration
Disclaimer, I don't have SQL Express 2005 installed but I think the settings are found in the same place in 2008. If the info here is not exact to SQL Express 2005, the general terminology used here should be enough to get you headed in the right direction to find the specifics.
While viewing the database in Server Management Studio or Enterprise Manager, right click the database server instance name (the root of the tree) and select properties. There should be a section title Connections and within this section there should be an option "Allow remote connections to this server". Make sure it is checked. The other setting you need in this properties menu is under the security area. There is a radio button for "Windows Authentication Mode" and "SQL Server and Windows Authentication Mode", you want the second that allows both.
The next step you have may be to create a new user, add a password, and connect the user to the database. That will give you the credentials you will use in your database connection string while programming. I usually add new users through the security section of the database then set the User Roles for each database that I need to connect to. It is good practice to limit the permissions to those needed by the application. Typically this is read and write, but sometimes you can get away with just read. The less the better.
I am currently running SQL Server 2005 Standard Edition on a Windows 2003 server machine.
I have gone to the properties of the server and confirmed that the Login Auditing is set to both failed and successful logins. For some reason though there is nothing in the logins for fails or successes in the SQL Server logs when I know there have been logins for both.
I have searched out the reason for this and have not been able to come up with anything helpful, so I am hoping that someone here could give me a little direction. This is working on my other SQL Servers, so I know where to look for the results, but there are none there.
After speaking with Microsoft about the issue and doing much research, it was determined that this was an issue with the particular version of SQL (SQL Server 2005 Service Pack 2 9.00.3042) running on that particular version of the windows release. We reinstalled SQL, and then did all the updates and patches to both windows and SQL and this seems to have resolved the issue. The SQL logs are now tracking both success and failed logins.
Very new to SQL Server. I am needing to develop a SQL Server database to run with an iPhone app I am developing. It will ultimately be running with our full-fledged SQL Server database, which is administered by our IT guy, but I'd like to have a local database for testing.
Two questions:
I assume I can use SQL Server Express 2012 for this purpose, since it is advertised as such; but would it be better/easier to use what appears to be the simplest form, LocalDB, in conjunction with VB2010? It will be running on my office PC to which a port is open for TCP communication from my app (which is working fine). Would LocalDB work for that, if the communication occurs in the VB app? Or will I need to get the SQL Server Express edition?
If a prototype database is developed in SQL Server Express, can it migrate to our full-fledged SQL Server when the app is taken "live"? (I am not sure right now what version our full-fledged SQL Server is, but I was planning on using SQL Server Express 2012.)
Yes, the Express editions ARE the full-fledged SQL Server version - no code difference, only some marketing-driven restrictions (on database size and so forth).
You can absolutely develop your system on a SQL Server Express, and then just detach your database from Express and re-attach it to a Standard or Enterprise edition server. No fuss, no migration, no conversion - nothing - it just works. Period.
And I would probably even argue having a server installation (of your Express) edition is the better choice than LocalDB. That way, you're already using the server-based approach as you will later on in production, and you won't fall into any "convenience" traps offered by LocalDB (or other approaches) that make dev life easier - but rollout to production can be a challenge. When you use SQL Server Express as a server-based installation from the get to - you have the "real deal" from day one.