Is there a roadmap for allowing SSMS to connect to a PDW (MS SQL2012 Parallel Data Warehouse) with full functionality? Current support leaves much to be desired without installing third party tools.
View 3 RepliesI have new Dell XPS13 Laptop with Windows 10 Pro, which I plan to use for development. Â Installed vs2013 and SQL Server 2012. When running SSMS and invoking any of the tools, e.g. create new database, copy database etc. The controls in the dialog boxes are scrambled, i.e. overlaying each other or partially out of the viewport, making SQL Server totally unusable. Â Uninstalled SQL 2012 and installed SQL2016CTP3 and got the same result.
The display is Intel HD Graphics 5500 using a recommended 3200 x 1800 resolution. It appears that SSMS visuals do not scale correctly. Changing the resolution offers no support and in fact lower resolutions do odd things like leave snail trails and do rapid flashing screen repaints.
I am getting an intermittent problem with executing queries on my workstation. Whenever I execute a couple of store procedures that return a large numbers of rows (200,000 to 500,000 rows) I receive an intermittent error message when running the same sp with the same parameters sometimes the procedure runs fine and returns the result, sometimes I get an error message
Error message is: Index was outside the bounds of the array.
Sometimes
Error message is: Internal connection fatal error.
Sometimes I get a datetime overflow
I also occasionally get these intermittent messages when I execute the native query that the SP wraps.
I have SSMS 2015 SP1 installed on my workstation, the servers are a range of server from 2008 R2 SP2 to 2014 SP1. It feels like a client problem as there are applications connecting to these servers and running the stored procedures without issue...
I have many tables, and I just want to print the relationships between them. Â The ones without foreign keys to primary key relations are irrelevant. Â I made a diagram of all tables in sql server management studio, and it shows the key relations, but its a very large diagram horizontally and vertically. Â Is there a way to print the whole thing so that it doesn't take endless pages that I don't know how to piece together?
View 3 Replies View Relatedtrying to run ssms.msi failed with code 29506....then i am trying to use command line but i do not know  how to do this.
View 4 Replies View RelatedWould it be possible to get a multi-database functionality on the same instance option available in SSMS anytime soon?
View 6 Replies View RelatedWhen I run the parse command in SSMS, it merely does a syntax check. When I run through the export data wizard by right clicking on a table, it allows a query as the data source. When I click on the parse button in the window that accepts that query, it resolves object names and notifies me of invalid ones. I'd really like the same thing to happen when I parse in SSMS...
View 5 Replies View Relatedis there a way to change SSMS 2012 default query save location?
Scenario:
1. Open SSMS
2. Create new query
3. Click Save
I see "DocumentsSQL Server Management Studio" folder, but I want to change it to be "d:". How do I do this?
I tried:
1. [URL]- in folder "DocumentsSQL Server Management StudioSettingsSQL Server Management Studio" there is a file NewSettings.vssettings, setting it to "d:" or "d:" didn't work.
2. Changing HKEY_CURRENT_USERSoftwareMicrosoftMicrosoft SQL Server100ToolsShell VisualStudioProjectsLocation didn't work too. There is no "Shell" under "110Tools"
Did I do something wrong, or is there another way?
Just installed SQL Server 2005 Standard. When I attempt to connect using SSMS it just sits. No error comes up. The log seems to indicate everythings OK. SQLServer and SQLBrowser services are started. Here's the log:
2007-07-07 09:41:23.07 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2007-07-07 09:41:23.07 Server (c) 2005 Microsoft Corporation.
2007-07-07 09:41:23.07 Server All rights reserved.
2007-07-07 09:41:23.07 Server Server process ID is 2412.
2007-07-07 09:41:23.07 Server Authentication mode is WINDOWS-ONLY.
2007-07-07 09:41:23.07 Server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'.
2007-07-07 09:41:23.07 Server This instance of SQL Server last reported using a process ID of 1348 at 7/7/2007 9:35:40 AM (local) 7/7/2007 2:35:40 PM (UTC). This is an informational message only; no user action is required.
2007-07-07 09:41:23.07 Server Registry startup parameters:
2007-07-07 09:41:23.07 Server -d C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf
2007-07-07 09:41:23.07 Server -e C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG
2007-07-07 09:41:23.07 Server -l C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf
2007-07-07 09:41:23.11 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-07-07 09:41:23.11 Server Detected 1 CPUs. This is an informational message; no user action is required.
2007-07-07 09:41:23.34 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2007-07-07 09:41:23.36 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-07-07 09:41:23.89 Server The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed transaction functionality, please start this service.
2007-07-07 09:41:23.89 Server Database mirroring has been enabled on this instance of SQL Server.
2007-07-07 09:41:23.90 spid5s Starting up database 'master'.
2007-07-07 09:41:24.20 spid5s SQL Trace ID 1 was started by login "sa".
2007-07-07 09:41:24.28 spid5s Starting up database 'mssqlsystemresource'.
2007-07-07 09:41:24.31 spid5s The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2007-07-07 09:41:25.65 Server A self-generated certificate was successfully loaded for encryption.
2007-07-07 09:41:25.67 Server Server local connection provider is ready to accept connection on [ \.pipeSQLLocalMSSQLSERVER ].
2007-07-07 09:41:25.67 Server Server local connection provider is ready to accept connection on [ \.pipesqlquery ].
2007-07-07 09:41:25.67 spid9s Starting up database 'model'.
2007-07-07 09:41:25.67 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2007-07-07 09:41:25.67 Server Dedicated admin connection support was established for listening locally on port 1434.
2007-07-07 09:41:25.68 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2007-07-07 09:41:25.68 spid5s Server name is 'LAPTOP'. This is an informational message only. No user action is required.
2007-07-07 09:41:25.71 spid12s Starting up database 'msdb'.
2007-07-07 09:41:25.71 spid13s Starting up database 'ReportServer'.
2007-07-07 09:41:25.71 spid14s Starting up database 'ReportServerTempDB'.
2007-07-07 09:41:25.71 spid15s Starting up database 'testx'.
2007-07-07 09:41:27.45 spid9s Clearing tempdb database.
2007-07-07 09:41:28.65 spid9s Starting up database 'tempdb'.
2007-07-07 09:41:28.78 spid5s Recovery is complete. This is an informational message only. No user action is required.
2007-07-07 09:41:28.78 spid12s The Service Broker protocol transport is disabled or not configured.
2007-07-07 09:41:28.78 spid12s The Database Mirroring protocol transport is disabled or not configured.
2007-07-07 09:41:29.25 spid12s Service Broker manager has started.
2007-07-07 09:57:23.54 Server CPU time stamp frequency has changed from 117988 to 200203 ticks per millisecond. The new frequency will be used.
2007-07-07 10:09:23.85 Server CPU time stamp frequency has changed from 200203 to 242307 ticks per millisecond. The new frequency will be used.
2007-07-07 10:20:03.20 spid12s Service Broker manager has shut down.
2007-07-07 10:20:04.25 spid5s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
2007-07-07 10:20:04.25 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
I've installed SQL Server 2005 SP1 RTM on a Windows 2003 R2 machine (machine A), and my local workstation (machine B).
From machine B, I can use SSMS to connect to SQL Server on machine A. This is using either "New Query" or "Object Explorer".
However, on machine A, SSMS can only connect to machines A or B using the "New Query" option. If I try "Object Explorer" for either, I get the error message "Failed to retrieve data for this request... urn could not be resolved at level Configuration."
I'm not sure what died (no pun intended) since the last time this worked. Any thoughts on this?
We are running SQL 2005 Standard on Windows 2000 Server Standard. We are trying to connect via SSMS with the Object Explorer to the server and it is failing with an error message stating:
"An exception occurred while executing a Transact-SQL statement or batch.
Additional Information:
Error executing extended stored procedure: Invalid Parameter (Microsoft SQL Server, Error: 22001)
Using profiler, I tracked down that it is a call to xp_instance_regread. This is something that SSMS is issuing - not me.
We've found in the past that rebooting the server fixes the problem. But it keeps cropping up. The only thing running on this server is SQL 2005 - so if something is monkeying with the registry - it's got to be SQL Server itself.
Querying works just fine - we can use the editor to perform queries without any issue - it's just explorer that goes kaboom.
We have SP2a installed on the server and on most (if not all) of the clients.
This is getting frustrating because it's a production server and we're having to reboot this to fix it.
Hi,
In a nutshell I'm unable to connect to SSRS within SSMS yet I can connect to SSIS, SSAS and the Database Engine within SSMS from the same named server instance ("BOODEMO")
"SQL Server 2005 Surface Area Configuration" reports that service status SSRS (DEMO) is running.
The only other problem that I have found which may be linked is that within "Reporting Services Configuration Manager BOODEMO" there is a red circled crossed next to "Report Manager Virtual Directory", yet this application has just recently reported that I successfully created a virtual directory.
Any help or constructive guidance would be greatly appreciated.
Thanks in advance,
Kieran.
Every time I start SSMS 2012 the "Connect to Server" box is partially obscured in that the top of it, the move bar can't be accessed. I've manually moved it using "alt+space" then "M" followed by the arrow keys, but it's getting annoying. Â Is there any way to change the initial start position of this box?Â
View 6 Replies View Relatedhi guys,
do you know if we can use sql authentication to connect to SSIS through SSMS. right now it's only windows authentication, and SQL authentication is grayed out.
Not sure if this question has already been answered because it sounds like easy question.
I am working with SSRS. I do have admin rights. I can connect to the url https://localhost/Reports and can create the new reports and subscription. Delete the reports and subscriptions.
But when I tried to connect to Reporting Services from SSMS, I am getting below error.
I used the windows authentication. It is showing that the user name or password is not valid or you don't have permission to access this server
I can connect to the database engine and Integration services but unable to connect to the Reporting services.
Hi,
I am able to run an SSIS script from BI Visual Studio no problem, I am also able to connect to SSIS within SSMS successfully. I have system access rights to the Database Engine of the same server name.
However I have a user who also has full system access rights to the Database Engine of the same server name. However he can only connect to the database engine, he cannot connect to SSIS within SSMS, but he can successfully execute a SSIS script within BI Visual Studio which is targeted to the same server name which he can€™t connect to within SSMS.
Any help would be greatly appreciated.
Kind Regards,
Kieran.
I recent installed a named instance of SSRS 2005 on a remote server. The server has a side by side install of SSRS 2000 and SSRS 2005, with the SSRS 2005 being a named instance. The server also has SSL and MS Sharepoint Portal Server installed.
When I try and connect to the SSRS 2005 instance with my client install of Mangement Studio, I get the error message:
"The underlying connection was closed: Could not establish a trust relationship for the SSL/TLS secure channel. (System.Web.Services)
Additional Information: The remote certificate is invalid according to the validation procedure. (System)."
Obviously, this is a SLL issue, but, not being a security guru, I have no clue on how to fix this. I do know the certificate is valid, not expired and properly working. Both installs of SSRS are set up using the SSL certificate. Also, I am not connecting to SSIS with Management Studio, as I heard there is a bug connecting to both SSRS and SSIS at the same time.
Anyone have any ideas?
Thanks!!
Jeff
Version: SQL SERVER 2012 enterprise edition and SP2.
Due to one of the security reason, I have changed default port 1433 to another port number in configuration manger tools->protocols for MSSQLSERVER->TCP/IP --> IP ALL section mention another port number.
After restarted service, SQL SSMS able to connect server itself and new port number also LISTENING.
But SQL client SSMS not connected to one of the PC side after changing default port.
I've two instances(Default, Named[dynamicsFINANCE]) running on SQL server 2014. However, when I try to connect to named instance say (dynamics FINANCE) using SQL authentication from local SSMS, I get below error message.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. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)I assigned a static port number to the named instance [dynamicsFINANCE]Â 1450. I also setup the firewall rule to allow access to Port 1450.
View 4 Replies View RelatedI have installed a SQL Server 2005 Standard Edition instance with SSIS on Window Server 2003 x64. From my PC, I am able to connect to the Integration Services on the server using Windows Authentication but not with a local SQL login - and the option to change authentication methods is greyed out.
Is it possible to remotely connect to SSIS using a SQL login rather than a Windows login? If so, any ideas or references for configuring it as such?
Thanks.
- Lance
Hi,
I have gone through so many kb articles to understanding the problem, but no luck as yet.
Here is the situation:
I have two dev servers : Server A and Server B. Both are set up in an identical fashion. Windows 2003 sp2, Sql Server 2005 sp1 Developer Edition, both are on the same domain, Both have all the three protocols enabled: Shared Memory, Tcpip, and Named Pipes in that order. I can ping both servers, and telnet using the default port. Both have only default instances. Both use the same domain user account for sql service. Both have the error in the log saying that spn could not be registered so authentication may fall back to NTLM.
Here is the issue: When I try to register Server A specifying tcp-ip connection, I am successful and I can see that the authentication is NTLM - is as expected. since the spn registration did not happen and since the sqlservice account is not a domain admin, the authentication used NTLM over tcp-ip. However, I try to register Server B specifying tcpip, I get a cannot generate sspi context error. Why did the authentication not fall back to NTLM as in Server A? From what I read in the KB articles, I asked our network admin to check up the spn, but he assures me that spn were never manually registered.
Can somebody throw more light on this issue?
Thanks
KRSE
Error: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) (Microsoft.SqlServer.DTSRuntimeWrap)
Â
Here are the steps I followed:
To configure rights for remote users on Windows Server 2003 or Windows XP
I need to install SSIS/SSRS in SSMS. I have connected the SharePoint list view to excel for reporting purpose but due to data size the performances is very slow in excel and now I would like to connect the SharePoint List to SSIS/SSRS
I have windows 8, 64 bit system
I have installed SQL Server Management studio 2012 but I am unable to enable the Integration and Reporting Services
May be I have missed to choose the option during installation.
Basically, I am asking if it is possible to use SSMS (Query Analyzer window) with Informix. I am thinking linked server. If I have the ODBC driver installed on my workstation (win 7 pro VM workstation -- SSMS on same VM machine) is this doable? Do I just do the standard linked server routine or is there a special way (if it is even doable).
View 4 Replies View RelatedI need to connect to Active Directory in a stored procedure to try to verify if a user exists. code snippet to do the same?Â
View 5 Replies View RelatedSomeone please help me before I loose all of my hair :mad: !!!
I have two machines, a Windows Server 2003 machine running an SQL Server Standard Edition database instance and client tools (Enterprize Manager etc.), and a workstation PC running Windows XP SP2 which has just the SQL Server client tools (not an actual DB instance).
I'm trying to use the Enterprize Manager client tool on my WinXP machine to remotely connect to the server instance on the server PC (via 'New SQL Server Registration' option). Everytime I do this I get the following error message:
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server Connection.
Now I've tried using different usernames and passwords. I have login details for my SQL Server set to use Windows Login rather then SQL Server login, so I tried remotely connecting with the username and password for the server PC, tried 'sa' with server password, even tried setting up a new user on the server and logging in from the client with that, no luck. I've opened up correct ports 1433 on both PCs, even disabled the windows firewalls algother. Both server and client have SP3a installed, WinServer2003 has SP1 and XP SP2.
So I'm at a loss to how to remotely connect to my SQL Server. FYI I know the server itself is working fine because I can connect to it using Enterprize Manager/Query Analyser on the local machine. Any ideas? Many thanks for your help!
I see we can install SQL Server 2016 CTP2 and Tabular SSAS.However, where are the tools to allow us to connect to the server and work with the tabular models?Supporting features such as bi directional filtering, etc..The existing SSDT BI tools for 2014 don't contain those additional features (editing relationship filtering direction for example).
View 2 Replies View RelatedI've two instances(Default, Named[dynamicsFINANCE]) running on SQL server 2014. However, when I try to connect to named instance say (dynamicsFINANCE) using SQL authentication from local SSMS, I get below error message:
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. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
I assigned a static port number to the named instance [dynamicsFINANCE] 1450. I also setup the firewall rule to allow access to Port 1450.
Hello,
After installing SQL Server 2005, I get a message stating "You must use SQL Server 2005 management tools to connect to this server", while trying to connect to my localhost using SQL Server 2000 Enterprise Manager.
Regards,
junior
We have just moved from 2000 to 2005 and ever time I try to open store procedure or function I was getting this error message...
[Microsoft][ODBC SQL Server Drive] To connect to this server you must use SQL Server Management Studio or SQL Server Management Objects (SMO)
So I installed "Microsoft SQL Server 2005 Backward Compatibility Components" from "Feature Pack for Microsoft SQL Server 2005 - April 2006" on the client machine and this resolved the issue. Specifically i installed the "SQL Distributed Management Objects (SQL-DMO) feature .....,
how I am getting following error message
[SQL-DMO]You must use SQL Server 2005 management tools to connect to this server
How can I disabled all other features.
Thanks,
Am customizing SQL server MGMT tools 2012 for Mass deployment.Client had asked to remove Customer Feedback option from help menu.how to disable that.
View 6 Replies View RelatedThe installation SQL 2008 R2 Management Tools on a Windows 7 workstation fails with the error, The specified account already exists.
Final result:Â SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
 Exit code (Decimal):          -2068052700
 Exit facility code:           1212
 Exit error code:              1316
Â
[code]...
I am running SQL Server 2005 x64 Enterprise under Windows 2003 x64 Enterprise. My current backup strategy uses T-SQL jobs run by SQL Agent (writes out *.bak files) and then I have an Integration Services job that copies the *.bak files to our NAS device. I have performed a restore without issue. The jobs are all automated every four hours via SQL Agent. Is this a sound strategy or are there additional benefits to using 3rd party tools? If so, what are the advantages and which tool provides them?