First of all: This is not opinion based, because I do not ask about "the best", but "any" alternative way to access a ravenDB.
I have a server which uses NServiceBus and RavenDB 2 as a database. Onto this server I cannot install silverlight, so the studio is not working. I also can not upgrade to ravendb 3 to get a html5-studio. (I will do that in future, but I need a fast solution on a productive system without causing downtime).
Is there any other windows tool available that allows me to access the ravenDB?
It's all just HTTP, so you can access the studio from another computer. You may need to update your Windows Firewall settings to allow access.
Related
I'm creating a VB-based application in Virtual Studio 2013, and up until now I've been testing the tables used for its operation in a local MDF file. Obviously, I need to find a better solution for deployment as this will need to be used by multiple users. I decided to go with a SharePoint list for ease of access and better local control. (We have SharePoint Server 2010 running)
When I try to add a SharePoint Connection in the Server Explorer, it tells me I don't have Foundation or Server installed. Checking our corp's software request tool, I didn't find either of those. There's a 'SharePoint Designer' option, and another that sounds promising is 'Microsoft SSIS SharePoint List Adapters with SharePoint'. I couldn't find any info online about whether those would fit the bill. Would either of those serve the purpose of standing in for Foundation or Server? If not, I'm sure I could find a way to request Foundation but I'm sure that would add quite a bit of delay while they vet it for business use.
Also, if I install the necessary software for development on MY machine, will those dependencies be included in the executable so my clients wouldn't have to install those SharePoint tools as well?
If you want to access and manipulate with your sharepoint list from your code, you can look at Sharepoint CSOM. It allows you to remotely connect and proceed CRUD operations with sharepoint list.
I had a engineer design our .net application back in 2009, my guess is that it was coded using visual studio, and all I have is the installer application. We have been using it on our 1 or 2 local client machines very well for the past few years, but now I want to move this front end to the cloud. Instead of installing it as an application on our windows 7 machines.
It is a very simple application used in our small warehouse that keeps track of cargo/shipments etc. It uses Sql Server 2008 Express as a backend which is stored locally.
I know how to get the database in the cloud, their are many options for that, using Amazon or Azure, but how do i get the local client application to the cloud?
I dont have access to the visual studio code, i just have the runtime executable file..
I am sure there is no way to do this, and many of SO users will say i need to re-write the front end.
I have tried to contact the developer and they hav since closed down. Is their anyway i can run this in the cloud?
I welcome all options and solutions!
Thanks.
I believe you have two options for hosting this application:
If you are able to configure the database connection string, you could host the database in the cloud, and distribute the application to your end users. However, you've already stated that you know how to move the database, so I assume this isn't an option.
The only alternative is to run the entire application on a cloud server, and send the user interface to a client using terminal services. This makes it appear as if the application is running locally on the user's computer, while it is actually running on the server.
For an off-the-shelf solution to achieve this, you could consider using Microsoft's RemoteApp Azure service. I'm sure there are other similar offerings available.
I'm quite a newbie, just trying to learn some new things. I've recently started learning c# etc and I'd also like to create a new SQL Server database using SQL Server Management Studio.
The thing is that for some reason I am not able to connect to the server. I might have done something wrong (or haven't done something that I should have done). Been researching the problem a lot on google and I found some tips but I still can't make it work.
I even found some installation tutorial in here: http://www.sqlcoffee.com/SQLServer2014_0005.htm and I only noticed that I used some different options (I used default, didn't change anything) like for example in "Database Engine Config" I chose "Windows authentication mode".
So that's what I get: http://imgur.com/2ftOdSB
Also I think I may have some problem with services, because when I go to the server configuration manager, the list is completely empty.
Thanks for any tips. If I don't solve this, I can always uninstall SQL Server Management Studio and reinstall it - this time following the steps in the tutorial. Hopefully that wont be necessary so help me please:)!
I've had a look at the link you posted about the installation instructions. As I mentioned before SQL server enterprise (database engine) won't install on a non-Server OS, You'll need at least Windows Server 2008. Have a look at msdn.microsoft.com/en-us/library/ms143506(v=sql.120).aspx for the system requirements. During the installation there must have been an option to install the database engine, but it was probably disabled because of your OS.
I suggest you uninstall 2014 Enterprise and download SQL Server 2014 express microsoft.com/en-gb/download/details.aspx?id=42299 and make sure you select database engine as part of the installation.
If you want to get into SQL, I would suggest trying out MySQL first. I've utilized it a little bit and found it to be fairly simple with a decent amount of documentation. This version of SQL will still function with various languages. It doesn't utilize Windows authentication, but rather lets you set a root password specific to the database itself. I don't know if your software is similar to that but there may be an option to not use Windows authentication and instead authenticate within the database software itself.
I have done some research, based on the problem that my single server gives me when I try to open a document library in windows explorer from the ribbon menu item "Open in Windows Explorer".
The same problem occurs when I try to map sharepoint to a folder in windows explorer too.
The error is:
Your client does not support opening this list with Windows Explorer
From the net, suggestions are:
(Since I'm trying this operation from server itself) enable Desktop Experience
Install the KB907306 update.
Enable IIS webDav service (Some say, it's just for additional functions from the MS Whitepaper)
(Edit) Started webClient service
I've already done them. Nothing changed. Proper machine restart and iis too have done.
Need some serious advice.
Thanks in advance.
Not sure if we are having exactly the same problem BUT I have had similar problem while accessing SP via Windows Explorer in Windows Server 2k8.
What I done to fix it is following:
Install new server feature called Desktop Experience (it comes with WebDAV redirector, which allows you to connect to WebDAV) - Note: Server will need to be restarted.
In Services start WebClient service (go to properties and make sure it starts automatically)
You will now be able to access your sharepoint via entering network path such as \sharepointhost\application\myawesomeapplication\ etc.
Hope that helps.
If you are trying to do this from the server, test it from a server which is not on the SharePoint farm (or better yet, a client machine). Ensure all of your testing is done from machines which are not on the farm.
Do NOT enable the IIS WebDAV service, as SharePoint provides its own WebDAV service and the IIS one overrides it in the pipeline. Enabling this service is a sure path to breaking WebDAV.
If you have SSL enabled, you may be in for a rough time getting it to work. Start by understanding how to use the 'net use' command, and the #SSL suffix.
make sure your webdav is installed as feature
make the following registry fix (http://support.microsoft.com/kb/841215) :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
Add a new DWORD "BasicAuthLevel" and change this to "2"
Restart your machine (and make sure it is enabled in IIS)
Make sure that WebClient windows service is running in the server. This shall appear in client operating systems like Windows 7, windows 8 however, on the server operating systems like Windows Server 2008, it shall be installed by enabling the server feature "Desktop experience" using Server Manager
This issue nearly killed me. I found that I was using a 64 bit version of my browser and that is'nt supported. I changed over to the 32 bit and it works.
We have a DB server with a couple web app db's on there (don't get a ton of traffic). We'd like to make use of the server and allow it to be the DB server for sharepoint. I'm assuming it's not good practice and that sharepoint should have it's own exclusive db server. Am I right in that conclusion, or is it alright if we put the database on a server that already hosts other databases.
You can install SharePoint on an existing DB server, sure. Unless your environment is going to be huge, I don't see why you would give it its own DB server. It will use an embedded SQL Server instance if you want, but you'll get better performance if you have the full-blown version. We're running a few SharePoint apps on our DB server with a number of other applications.
The way in which I solve this is to install a second SQL Server instance dedicated to SharePoint, as SharePoint likes to have a lot of control over the database and spews all sorts of stuff such as logins, etc. across the instance, which you really want to separate from your standard line of business instance.
The added bonus is multiple SQL Server instances on the same physical machine are included in your licence.
Be careful with the SQL Server collation. I think SharePoint requires a particular setting for this. See http://www.moss2007.be/blogs/vandest/archive/2007/07/24/sharepoint-2007-and-sql-server-collation-latin1_general_ci_as_ks_ws.aspx for one reference.
Prior to centralizing our environment we had many Sharepoint sites located on servers with existing applications. I'm not a fan of adding an additional named instance as this increases the administrative overhead for the DBA. You have to know how much use you expect of your Sharepoint instance then measure the resource utilization of your existing applications balance it from there.