Tag Info

New answers tagged

0

I was able to get this working with a similar work around: Put the server name and credentials into Credential Manager. It worked when I put in the computer name (reported from Control Panel\System and Security\System) without the port number. In our case, it was DEV-DB even though I can't resolve that name from my machine. I used the IP address to connect ...


0

Run the script to find out if there is any job running. If not then is safe to restart it. List Running Jobs /* DESCRIPTION: List the RUNNING jobs on an instance CONFIGURATION None Compatibility list: MSSQL2005 MSSQL2008 Does not work MSSQL2000 Legend @execution_status=1 Running @execution_status=4 Idle */ IF EXISTS (SELECT * FROM tempdb.dbo.sysobjects ...


0

Make sure your SQL instance is using mixed mode authentication. By default SQL is installed using Windows authentication only. From this MSDN page: To change security authentication mode In SQL Server Management Studio Object Explorer, right-click the server, and then click Properties. On the Security page, under Server authentication, select the new ...


0

Since you stated that the application runs correctly from your machine, you could test the following: Check if changing the connection string to work with local IP instead of hostname works Check if the application pool user on your local machine == the application pool user on the IIS Ping the hostname from the server to see if it resolves correctly If ...


0

This is most likely a permissions issue. According to sp_addscriptexec, to use sp_addscriptexec, the SQL Server service account must have read and write permissions on the snapshot location and read permissions on the location where any scripts are stored. To use sp_addscriptexec, the SQL Server service account must have read and write permissions on ...


0

First off, this is a terrible idea if this is your backup strategy for your SQL server. If you want monitoring of your backup process, then use a real backup tool. With the right one, you get monitoring, notifications, dedupe, and remote copies all in one place. But if you insist on continuing, forget trying to roll your own replication. If your SAN is ...


1

(Aside: I hope you're also running SQL Server backups. As in, from inside SQL Server. Moving right along....) This depends partly on the actual data types you use in your tables and they types of queries you more commonly run. For example, an integer column uses 4 bytes to store data no matter which integer you store there. A datetime uses 4 bytes to ...


0

Sql database are a bit like a big excel spreadsheet . There is column and line . When you remove data he don't shrink the database because he don't remove line and data , only the value (and he store in the log file the change if you are full log mode). You have to backup the database to reclaim space on log and storage file . (log and mdf) .


1

No, it shouldn't interfere. The alias is only needed on the servers or clients that will require the updated address. It can work in conjunction with any other names or addresses available without issue.


-3

DbDefence uses undocumented features to hide database schema even from DBA. Works in SQL Server 2005. They give away free version as well. If you just want to hide it slightly you can use "EXEC sys.sp_MS_marksystemobject"


4

The error message clearly says, that the error is due to Authentication failure. You need to enable Mixed-mode authentication. Once enabled, try to login and check the error message, if fails again. Try restarting SQL Server/Agent service with windows authentication credentials, to validate that there is no problem. Alternatively, try skipping the ...


1

The reason you're still able to run the profiler to read server-side trace on the SQL Server 2014 instance is because the server-side trace is still being generated, despite profiler (the GUI tool) not being included in the installation package for the web editions. That being said, 'Microsoft.SqlServer.Management.Trace namespace' is being removed from ...


0

You can. From Stack Exchange: select 'data source=' + @@servername + ';initial catalog=' + db_name() + case type_desc when 'WINDOWS_LOGIN' then ';trusted_connection=true' else ';user id=' + suser_name() end from sys.server_principals where name = suser_name()


2

Per https://msdn.microsoft.com/en-us/library/ms174396.aspx: LicenseType is Unused. License information is not preserved or maintained by the SQL Server product. Always returns DISABLED. This is true for 2005+, so it does NOT mean that you are using an unlicensed version, contrary to the previous answer.


4

Since you can see SQL Server running in process explorer, try right-clicking on the line referring to it, choosing properties, and choosing the image tab. The Parent may provide you with some insight as to what is starting the process.


0

I found that irrespective of the web server SPN configuration, I needed to create an SPN for the SQL Server using an HOST record for the SQL Server name, rather than a CNAME alias. That is, to cover all bases, I have added SPN's as follows; setspn -A MSSQLSvc/sqlserverhostname.example.org SQLServerServiceAccountName setspn -A ...


2

I had to configure the static ports for IP1, IP2, IPAll, Erase the 0 at Dynamic Ports and set TCP Ports to 1433, however, Im using a named instance. also open firewall ports Once you have static ports, you'll need to enable access to 1433 TCP and 1434 UDP. (Katherine Villyard) See Screen Shots for configuration details.


2

To steal from one of my own answers, :) I've successfully used this script to migrate hundreds of databases. (This script requires network connectivity between the servers.) @ECHO ON set controlfile=control.txt set oldserver= set oldmdfpath= set newmdfpath= set newserver= set oldlogpath= set newlogpath= set movedmdfpath= set movedldfpath= SETLOCAL ...



Top 50 recent answers are included