I would like to know if one can adminiter SQL server remotely using MMC on NT workstation? If so, how do you install the MMC and SQL Enterprise Manager Add-in on NT workstation?
I set up the collector, and specify the Run As as my AD account in the Collector Set - Properties - General screen. My AD account is the local admin of the remote server.
However, the collector does not seem to work. Although the collecting set is shown as running, the The blg file stays at 64K. If I open it, there is nothing inside (no counter at the bottom). What did I miss?
Are there any tools for administering SQL2000 remotely over the TCP/IP? And if this is possible what are the main hurdles on setting it up. Emulation is an option.
What is a secure way or accepted method to make database changes,IE: edit tables, add sprocs. ect. on a server being ran by an ASP.NET hosting service across the internet?
using remote admin program and i need to pul the entire DB onto my local maachine to do some trial runs. I have a static IP so i thought I could just DTS the how system to my computer. Can any one verify that this is the best way of suggest another? Thanks Matt
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?
I am getting problem with remote login to the sql instance.
In machine Sql 2008R2 is installed as default later 2014 installed as named instance. Both TCP/IP, shared memory, namedpipes are enabled for both named & default instances. For the default instance I can used the remote connections but the named instance is not allowing remote connections.
I'm experiencing problems connecting remotely (through the Management Studio) to a named instance of SQL Server Express 2005.
After investigation I determined it was a firewall issue - turn off windows firewall and I can connect fine. I initially added ports 1433 and 1434 to windows firewall - still no joy. Then I added the binaries explicitly (sqlservr.exe and sqlbrowsr.exe - or whatever they are) - still no joy. So, I looked into the firewall log to see what was being dropped. I found that my IP was trying to connect via port 1047 (TCP)... I've searched for anything about this on google and cannot find any indication that the management studio should be using this port to connect.
If I add this port, the connection works fine. Has anyone else experienced this ? As there seems to be no way of modifying the management studio to connect via a specific port, I'm a bit concerned that something is just not right.
We are in web site development company,Previously we don't have proxy configuration, after implementing Proxy , we have an issue to connect a remote database.
The error pops "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. Error 53".
I try to connect from a pc to a SQL Server on another pc. Both pc’s are in a workgroup. I want to connect from a Windows Forms application to a named instance on the other computer. By now I have been able to connect from one pc to SQL Server on the other with tcp:smurfin, 52782.
I want to be able to use servernameinstancename (instead of portnumber) to make a connection in a Windows Forms application.
I’ve checked / tried te following:
•In the properties of the instance, tab Connections, the option Allow Remote Connections is enabled •In Configuration Manager: TCP is enabled •The service SQL Server Browser is started •On the tab IPAddresses, in the section IPAll, there is NO portnumber for TCP Port. And TCP Dynamic Ports has the nummer 52782 •I have created un inbound rule for port 52782 and also for 1434 (SQL Server Browser). And to be on the save side: a rule for 1433 as well. •Restarted the service
If I run the following code in SQL Server, that same port number (52782) is returned:
EXEC xp_ReadErrorLog 0, 1, N'Server is listening on', N'any', NULL, NULL, 'DESC' GO SELECT local_tcp_port FROM sys.dm_exec_connections WHERE session_id = @@SPID
I am developing a package to restore a database from backup file on a remote server. I am having problems accessing the remote backup file when it is addressed via the admin share, in this case N$. It runs okay if a specific share is created but for some unknown reason fails via the adminshare.
I am executing the package job with a proxy account that is a member of the local administrators group on the remote server.
It appears that access via a remote admin share isn't possible from within a SSIS package. Is this the case?
I'm using ssms 2014, but got the same problem with 2012. I use ssms almost entirely on remote desktop sessions ( Windows 7, Server 2008R2, Server 2012 ). It may be related to having filtered job activity monitor windows open for hours, but about once per day ssms fails, and has to restart. Upon resuming usually only one of several queries is restored.
I want to set up a database role so that users can use sp_readerrorlog through SSMS. It does a check on membership in the securityadmin role.
I have tested it and can see you can grant execute on xp_readerrorlog but the SSMS GUI uses sp_readerrorlog.
I thought I could create a user/certificate and add the signature to sp_readerrorlog but it's not permitted (likely because it's not a normal database object).
So the other solution is to add the users to the securityadmin role but then explicitly deny alter any login (best done with a custom server role in 2012+ but otherwise just manually in 2008). I tested this out and it works, I'm not able to alter any logins or increase my own permissions, I also did a check of what's reported from fn_my_permissions(null, null) and it shows minimal permissions like I'd expect.
I recently installed VB6.0 Enterprise on my system. As a part of the installation is the option to install SQL Server 6.5 Development. I elected to install SQL. The install went without any glitches. Upon going into SQL Enterprise Manager, I was asked to register the server where SQL was running. My understanding was that SQL would allow me to register the name of my host system. (This is a stand alone system with VB6.0 and Sql development 6.5 installed - no network attached). SQL will not allow me to register my server's name as the host server. It says that if cannot connect to the named server. SQLSERVER and SQL EXEC services appear to be running without any problems. Anyone have any idea where I should start or what could be disallowing my connection/registeration of my server. Any help would be greatly appreciated..... Thanks... Tom
Developers wanting to access sql server developer edition on XP workstation in small office network (workgroup) will have problems using windows authentication (trusted connection) if the XP "server" machine has "simple file sharing" enabled.
Simple file sharing in XP can be disabled in control panel - folder options.
For this sneak mode to work accounts with the same user and password should exist on both "client" and "server".
Hi all!Is there any function in SQL that I can use to get current date fromworkstation? All functions which I tried (now(), getdate() etc.)returns current date from server but I need date from workstation.Regards,Mirnes Lemes
How can I configure my workstation running WIN95 to used the SQL Enterprise Manager from the server end and other utilities. I have installed the client network utility.
Reason to use enterprise manager because I wanted to perform administrative tasks on my workstation and I've installed SQL SERVER 7.0(Standard version with 5 clients)on the WINNT 4.0 server.
Hi all;I am trying to replicate our database by using the merge replication.[color=blue]>From server side I tried to connect to the workstation. I have[/color]installed MSDE to the client machine. I can see the machine name on theSQL Server Group however I wasnt able to create the conncetion betweenthe machines. I have checked my network connection, there is no problemI can see the machine and I can connect it through the network. I triedto use Client Network Utility with Named Pipes and TCP/IP but not agood news. I couldnt achieve to connect to the machine. So couldsomeone please help me out with this problem. I am really in trouble Ihave to find out this end of this week.RegardsAs
I've got VS 2008 Pro installed, as well as SQL Sever 200 (which I must keep installed). When I run the install for SQL Server 2005 developer edition, it continually fails to install
I had a perfectly good working copy of SQL Server 2005 installed. However, at some point I needed the Report Services Designer so I could edit my reports in Visual Studio. I inserted the CD and selected the feature from the list and it installed. Only problem being that it has completely removed my Management Studio and practically every other tool I didnt explicitly checked when installing the RS Designer.
When I tried to run the same Setup again and check everything, it tells me that there is no change between what I have selected and what is installed, which sounds like total bs to me, since my pc doesnt have a management studio etc anymore.
Out of pure misery I decided to remove my entire SQL Server installation, inc Instance, hoping to start anew and achieve the result I wanted with the least amount of frustration. I ended up here and followed it all the way: http://support.microsoft.com/kb/909967
When I started reinstalling, I ran into something new. The installer refuses to let me install anything but the Workstation components, books online and development tools. All the other options are greyed out and not even available.
Someone please help me get my SQL Server back up and running because I'm getting hopeless.
It appears that there is no way to install SQL Server 2005 Workstation Components on an x86 operating system (XP in this case) if you have the x64 install disks (Standard Edition). Can someone verify this?
I am finding it hard to believe that workstation components for a standard Windows client environment are not distributed with the version of SQL Server that matches Windows 2003 x64.
I have the following connection string in my Windows app that works fine on the Server: workstation id=SCSXP;packet size=4096;integrated security=SSPI;data source=scsxp;persist security info=False;initial catalog=nala But when I use that string on a workstation, it times out. I do have a Network connection to the Server. How should I modify the connection string to work on the workstation? Thanks, Bill
I am running SQL 7 (SP3) on a 2000 Server. When I configure the server as part of the Workgroup I have no problems connecting from the workstation. However, if I join the server to our 2000 domain, I cannot connect and/or register the server from the workstation through EM.
Is this a security issue? If so, what are the minimum requirements or what else am I missing. Any suggestions would be appreciated.
Hi again, could anyone tell me what to do about this...I'm not a dba but I do need direct access to the sql server such as scheduling new jobs (I can execute them immediately as pkgs or even run them as jobs on my machine, but to schedule I need to go to the server. The NT administrator does not like the idea of anyone else touching his server, so is there any way to circumvent the situation and do the scheduling from my workstation? Someone had mentioned creating an icon on my desktop but I'm not clear on the idea. Thanks a million. I get great help on this website.
I have installed SQL 6.5 client tool on to my workstation. Since then, we have upgraded to SQL 7.0 on our server. I installed SQL 7.0 client tool to my workstation and have been using it. I want to remove SQL 6.5 client tool from my workstation and do not know how. There is no uninstall button in the SQL 6.5 folder nor this program exists in Add/Remove Program in COntrol Panel. Can you help? Thank you.
Could someone please tell me what I have to set at the Server side so that I will be able to STOP and START the SQL Server using Enterprise Manager and `sa` login remotely, say from the workstation.
I have 3 NT Workstations that will not connect to my SMS database using NT Integrated Security. The SQL 6.5 server is set up to use mixed security. The only way to connect to the server is to use a standard sql account. Any ideas? THis happens to all users even administrators.
I have Vista Ultimate (IIS Enabled), SQL Server 2005 Developer Edition (downloaded and ran the SP2 Update), Visual Studio 2008. VS2008 installs no problem. When I install SQL Server 2005, I get an error when it trys to install the last part( Workstation Components, Management Studio, etc). I have tried FULLY, MANUALLY removing all SQL products and registry entries. I have used Windows Installer Cleanup Utility. I have tried Microsoft's recommended way of manually removing SQL Server 2005. If I manually run SqlRun_Tools.msi the error comes up right away.
The error is: "A component that you have specified in the ADD_LOCAL property is already installed. To upgrade the existing component, refer to the template.ini and set the UPGRADE property to the name of the component."
Here's the Setup Error log: http://toby.pastebin.com/f63405e24
This might not be a SQL Server question, might be something else. Ihave a workstation on a LAN that can't connect to the SQL Server. WhenI try to configure a User DSN to connect to it, the server name I wantappears TWICE in the list of possible servers. No matter which one Iselect, it can't get the connection.The workstation also can't connect through EM or QA.We've checked the user's permissions, we've re-installed some serverpacks, re-installed the Client Tools, we've even hunted through theregistry, everything looks OK, but we still can't connect. This is theonly machine on the LAN that can't connect. Everybody else connectsfine.I'm stumped. Any ideas? Anybody ever seen the server name appeartwice like that?-Emily