Hello All,
I have a question in regards to Remote MSSQL Management. I am currently using EMS SQL Manager for SQL Server, the lite version and I find it to be rather slow sometimes. Has anyone used this program? If so, is it faster in the purchased version?
Also I've heard a lot of people use Win SQL, which is better? Is there anything else out there better than these?
My employer has asked me to search for which remote management tool we should purchase. Any recommendations would be greatly appreciated. Cost is not a huge issue, but obviously the best bang for the buck is what they are after.
Hi guys, I don't own a copy of Enterprise Manager and I need to remotely restore a database on my local machine to my hosted machine, can you guys recommend an application that can do remote restores?
Or is there a way to convert a Database into a long set of Transact SQL statements that I can run on the remote server (ala MySQL's MySQLDump)?
An ASP.NET website hosting service allows the use of Enterprize Manager to manage the backend database of a hosted asp.net website. This is not done across a VPN and I don't think it could be done on SSL so the question is : How Secure is that? would this be ok for learning but not Ecommerce? Or is it an encrypted session and I paranoid?
We just installed an application, WhatsUpGold, to monitor our servers. Management won't let me host that on my primary SQL box. So, we are using MSDE on the local machine (call that box my_netmon).
I can access the db with very basic functionality using osql while on the my_netmon machine. I've added my domain user account as a System Admin using the following commands.
exec sp_grantlogin @name go
exec sp_addsrvrolemember @name, 'sysadmin'
But when I go to the my_sql machine and try to attach to it with Enterprise Manager I get an error that the server does not exist.
What gives??? Is it just not possible, or am I missing something here?
My goal is to just be able to see the data stored in the MSDE db. Write views, etc...
Recently had to rebuild our SQLServer installation from scratch! major pain!! We had a remote server running a replicated version of the internal database system for the website. We also have a SQL DB hosted with a new ISP which is in test mode. All managed via EM.
Re-installed software, upgaded tp SP3, new MDAC. Set up the references for the two external DB's with the Client Network Utility. In EM set up a connection to DB on the new ISP, works perfectly, tried on the old DB and get 'SQL Server is not running or access denied' error message.
I confirmed the server is running, as its our live site. Cant connect using Query Analyser. I can ping the adress successfully. I've created new user logings that mach on both machines/servers, still no luck!
Can anyone suggest what the problem is/might be or how to fix... I'm flat out of ideas!
I have just put up an Webserver with SQL Server 2000. Everything is working fine on the remote machine Thru TS .. i can do every administrative things .. But i m facing problem to connect my remote databse server thru the Enterprise Manager .. It Gives me Cant Connect Database Server " Connection Failiure " when i try to connect my remote database server thru Ip address ,.. Please some one help me out to make connecting database server thru Enterprise Manager ..
Hi all,I need to gain access to a remote SQL Server 2000 storing my data.The remote SQL machine can only be accessed via an internet connection,that is - it is not part of my network.I know Enterprise Manager can do the job, but EM only comes bundled inMS SQL Server, which is not installed on the client machine.Please let me know which other (preferably free) tools can performsuch remote access.Thanks,Gilad Haimov
i am trying to consume an webservice which under secure layer (HTTPS)
eg: https://test.com/test.asmx
i'm connected thro' a proxy server.
when i use the same url in IE it works fine, but when i connect thro' http connection manager it always throws me a error saying "unable to connect to remote server "
can anyone provide me solution to over come this problem
I'm trying to run an SSIS package. The package runs on an SQL 2005 server on Win2k3 server. The package tries to connect to another win2k3 server with sql 2000 to retrieve some data. However, I recieve the errormessage shown in the topic.
I found info about modifying the MSDTC security settings under "component services" and did so. I made sure everything was allowed. However, the result was the same. Does anyone have any other idéa about what could cause this problem?
PS. The package works fine if I set up both databases on the same physical machine...
A user was created with a limited privilege under the USERS group. Once this user loged in the Report Manager he is acting like an Admin and Content Manager, though he is not given even a browser role.
What do u think that this guy is acting like a Super User evenif he is restricted to a browser role on the Report Manager ????????????
On one of our machines, all of the SQL Server 2000components except for the main Server component (SQL Servercore) itself were installed (Management tools, etc) a while agoand everything was running fine. Now I go and add/install theServer component and then Service Pack 3a.It seems that Service Manager won't start up (I get an hourglass cursor)and now I find that Enterprise Manager won't run as well. No errormessages appeared and I don't think I saw anything unusual inthe log file.However, I can use Enterprise Manager on a differentmachine and connect to the database (so the databaseitself seems to be running).Any suggestions as to what the problem might be and how tofix it? I like to see if I can repair this without havingto do a reinstall.Thanks.PF
IF someone can assist me. Everytime I load up enterprise manager the service manager turns off. And the enterprise manager can't connect to the local database. But everytime i turn it back on and try to connect again it shuts it off and around and around we go. Help would be appreciated. Thanks.
- When I disable "allow remote connections to this server" from server properties>connection page, I can still remotely connect to the server from SSMS...so what is the impact of enable/disabling it?
- what is the impact of changing the remote query timeout (on the same page) from default value?
Fellow Devs, I have an instance of SQL Server Express 2005 running on another box and I have Remote Connections enabled over both TCP/IP and Named Pipes, but on my other box I keep getting the error that the server does not accept Remote Connections. Any ideas why this might be happening? Is there some other configuration?
HiI'm going insane.I have a club starter kit on my local server which is working fine.I have migrated the database to my remote host and seems to have transfered ok.For a brief period I was able to connect to the database remotely, but now I cannot I get the following, even though SQL Server Surface Area Config is set to accept remote connections.An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)This is my connection string;<add name="ClubSiteDB" connectionString="Data Source=xx.xxx.xx.xx,xxxx; Network Library=DBMSSOCN; Initial Catalog=tets; User ID=sqladminbob;Password=sqlbob4398;" providerName="System.Data.SqlClient="/>I hav also tried to use aspnet_regsql.exe to add the remote provider but I get the same message. Thanks
I am using SSIS 2005 on Windows 2003 server. Using Excel Source to dump the data for staging database. I am getting following error while I execute it through BI studio's execute button.
I have deployed my packages into Sql Server and I am using Configuration File. As my Data Source is Excel, I have changed the connection string during deployment with Server Path. But I am getting the following errors. Actually the File Exist in Path. May I know What is cause of the issue? Do I need to give any permission to execute the package.
SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
component "Excel Source Service Contract Upload" (1) failed validation and returned error code 0xC020801C.
One or more component failed validation.
There were errors during task validation.
DTS_E_OLEDBERROR, Error Code: 0x80004005 Source: "MS JET DB Engine" Description : Path is not valid
I am trying to add a linked server from a AMD x64 server (Windows 2003) with SQL Server 2005 64 bit to a Server running SQL 2000. These are not in the same domain.
I can create a linked server using the option "Be made using the login's current security context" but can not when trying to specify the security context, i.e. sa and the sa password. When I try I get the following message:
Msg 15185, Level 16, State 1, Procedure sp_addlinkedsrvlogin, Line 98 There is no remote user 'sa' mapped to local user '(null)' from the remote server 'DTS_FSERVER'.
I have several other x64 server that I have no problem creating a linked server and specifying sa and the sa password.
The problem with using "the login's current security context" option is that I get an error when trying to run any Jobs against the linked server. The job fails withe the following error:
Executed as user: NT AUTHORITYSYSTEM. Access to the remote server is denied because no login-mapping exists. [SQLSTATE 42000] (Error 7416). The step failed.
I'm sure the two errors are related. Any ideas what is going on?
I am working on SQL Server 2005 (x64) with Windows Server 2003 (x64) operating system. I am having a major issue in SSIS. Here is the detailed explanation of the issue :
I have an EXCEL file in 2003 / 2007 version. It contains some data. I want to import the data using SSIS into SQL Server 2005 (x64) database table. I have taken "EXCEL FILE SOURCE" and "SQL Server DESTINATION". It was failed on importing data. Surprisingly it works fine in SQL Server 2005 (x32). Can you please explain why it is NOT woking on (x64) ?
Here is the error code i am getting:
[Excel Source [1]] Error: The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009.
I just want to find out what the difference between a remote login and a remote query is. I'd have thought that a remote query inherently requires a remote login.
Has anyone seen this error? It comes up when my app executes a select statement via linked server (from MSSQL 2000 to 2005) the second time it runs. It's basically a timed poll of tables in the remote database. It works once but the second time it executes I get the error from the remote db, it's just a select but I guess the cursor is still open so it can't run again. After the exception the select will run again, once and it just repeats. I have researched it a little and it looks like it mostly has to do with the isolation level of the transaction. Unfortunately based on the componet being used to access the database I don't beleive I have the ability to use transact SQL to call the isolation level (s) listed.
Here's the weird part though, at another site the same scenario is running fine. Same primary and remote db versions of MSSQL as well as the application and it runs fine. I guess my question is what type of setup parameters that may be defined in MSSQL 2005 for the remote database might make it behave in this manner in one instance and not the other? TIA in advance for any thoughts/assistance.
I have an SSIS package that I need to modify. It was developed in Visual Studio 2005 and runs faithfully in production on SQL Server 2005. Suddenly, I can't open the package on my own workstation. I see a big red "X" image and a message stating "Microsoft Visual Studio is unable to load this document." The real reason the document can't be loaded appears to be:
Error loading DataWarehouseLoader.dtsx: The connection type "OLEDB" specified for connection manager "Warehouse Logging OLE DB" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.
Does anyone know what causes this and what I can do? The package has been in production for 9 months and I've never seen this problem before.
I'm new to MSDE and WebMatrix. My problem is that I can't find a way to load a MS SQL Server 2000 schema with WebMatrix. So I guess I need a program that manages that kind of things.
This is going to be a very newbie question. :) I am just wondering if there is anything that provides a GUI inferface to manage MS SQL? (Like PHPAdmin for MySQL..)
