17

It's because I was connecting to the SQL Server locally, from the same server that hosted SQL Server. When I connect from another machine on the network, the authentication mechanism used is Kerberos, as expected. SQL Server will always use NTLM if connecting locally. Kerberos is only used if connecting remotely. This post from the SQL Server Protocols ...


17

Here's a solution I just found to this old issue: Stop all SQL services Start with -m Run MSSQL Management Studio As administrator If not started as administrator (as I wasn't), then you'll receive the generic an admin is already connect. Instead of saying you can't connect because you aren't an administrator. Another confusing error from Microsoft. I ...


10

To add to Ben Thul's answer, this can be accomplished remotely fairly easily via SQL Server Management Studio's GUI. Under the Object Explorer for your database -> Programmability, right click on Assemblies and select 'New Assembly...'. Browse to your updated DLL. Instead of clicking 'OK' (which will fail, as an assembly of the same name already exists) ...


5

Looks like TFS 2010 isn't even supported on Windows Server 2012: http://msdn.microsoft.com/en-us/library/dd578592(v=vs.100).aspx. Anyway, an in-place OS upgrade on a server hosting SQL Server and TFS is something I'd really prefer to avoid.


5

If SQL Server Web is running as LocalSystem while instead SQL Server Express is running as NetworkService, then it's perfectly correct that SQL Server Express doesn't have write permissions on the database files, because the NetworkService account doesn't have administrative rights (although, based on the ACLs you posted, it shouldn't even have read ...


4

This article explains the issue pretty well: https://technet.microsoft.com/en-us/library/ff658546(v=sql.100).aspx. I am using Failover Clustering for most of my highly available DBs (both Oracle and MS SQL). In order to build a cluster you need either a separate SAN/NAS serving as a shared storage for your hosts or use some free 3rd-party mirroring solution ...


3

You cannot run SSIS package on a release that is below the developed level of the package, so it is not possible to deploy from SQL Server 2012 to SQL Server 2008 since SSIS packages are not backwards compatible. This the SSIS engine issue. See more here: Interoperability and Coexistence (Integration Services) From the documentation: On an instance of ...


3

Looks like you want this msdn page. Basically, you're limited to 1 CPU, 1 GB RAM usage, 10 GB database size, no high-availability options, and the bare-bones basics in every other category. (Regarding the backups, I believe it's doable, but you'll [probably] have to use the SQL Management Studio provided with a proper SQL edition to set those up.)


3

I was diagnosing a similar issue implementing Ola's scripts. It would work on some servers and not others. I would get: "Msg 50000, Level 16, State 1, Procedure DatabaseBackup, Line 395 XXX The directory does not exist." In my case the problem was that although SQL Agent was running under a domain acct with sufficient privileges SQL Server itself was not. ...


3

You mention that the connection takes a long time - once the connection is established do operations / queries proceed at a normal speed? If it's just establishing connections that are slow but you can receive result sets at a normal rate I would make sure there are no authentication issues like the site is not properly defined for the database server and it'...


3

How can I create a network between these 2 computers for file sharing? Connect them both to the same router at the same time. Can I access SQL server installed on 1 computer from 2nd computer? If yes, how? Yes. There's nothing special you need to do. Whatever tool you are using should let you specify the server you want to connect to. Specify the name ...


3

Yes. Go to View -> Registered Servers. Go into Database Engine -> Local Server Groups and create a new server group. Add all the servers you want to that group. Highlight the group, then right-click for a new query window. Any t-sql you run will be executed on all servers. (If you want to test this, use select @@servername.) So, your jobs. When ...


3

After double-checking the parameters I choose when reinstalling, I realized that Mixed-mode wasn't checked, only Windows authentication mode. Following the instructions to this link fixed my problem: https://msdn.microsoft.com/en-us/library/ms188670.aspx (I'm quite impressed by the clarity of the Microsoft error message in this simple case)


3

Check if the issue exists on the localhost of the server to eliminate the possibility of it being network hardware causing the timeout. Assuming the issue goes away when you test on the localhost, then it may very well be network related. You mention a 23 ms latency when checking a traceroute every 1 minute. 23 ms doesnt seem like a LAN connection and most ...


2

If all they need is db_owner, then I'd recommend that you do this in your existing instance. Creating a new instance incurs the overhead of running two copies of all the SQL binaries. SQL works best when it can govern all the available resources of the server. Multiple instances are not aware of each other, and can end up fighting for available resources. ...


2

You're looking for VIEW DEFINITION. You can grant a principal VIEW DEFINITION at various scopes (server, database, schema, specific object). Example for a stored procedure: Use MyDB GRANT VIEW DEFINITION ON p_MyProc TO SomeUser For all objects in a database: Use MyDB GRANT VIEW DEFINITION TO SomeUser For all objects on the server: USE master GRANT ...


2

My best guess is that this is related to permissions for the account that the SQL Server service is executing as. It looks like others have seen this issue before, and if the service account can read the files you're attaching but not write to them, the database will be in a read-only state.


2

The issue has been resolved. I created a new network share location, giving it very open permissions (everyone:Full control), and the backup works to that location. Whatever the issue is, it must be isolated to NTFS/Share permissions on the target. I dont' know why several of my clients were all having the same issue, but this fix worked on all of them. I've ...


2

Who is the job running as? Is it running as a domain user who has access to the shares in question? Or is it running as SA? If it's running as SA, it's running as your SQL Server Agent account. Make sure that the user running the job is able to access the network share in question. Also, the command in particular should be SERVER\INSTANCE, not SERVER\...


2

In order to update sys.brickfiles manually, you're required to use the Dedicated Administrator Connection. This is available via SQLCMD; you just need to type ADMIN: before the servername. [Insert generic warning about being careful and having backups here.] Conversely, you could loop through a list of databases and change the autogrowth settings that ...


2

Assuming I don't want any new features of 2012 is it as easy as restoring the 2008 databases on the new server? It is - plus setting trace flags for the server to force the old behavior of the query optimizer, I think. If that works, I guess it's not the recommended way, Why not? It totally looks like the recommended way to me.


2

I think I have some idea what you might want to do... I think you might be asking how you can have a website you host target an arbitrary MSSQL server. There isn't really a good way to do that. You could, I suppose, have your client specify their MSSQL connection string to your application; how you might do that depends on your application and whether it ...


2

2018-05-02 16:32:47.80 spid10s FCB::Open failed: Could not open file e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1. OS error: 3(The system cannot find the path specified.). 2018-05-02 16:32:47.80 spid10s Error: 5120, Severity: 16, State: 101. 2018-05-02 16:32:47.80 spid10s Unable to open the physical ...


2

Fortunately, Microsoft stopped releasing updates the way they did back then, so a system doesn't need to install 300+ updates. For the base operating system, all you need is the most recent servicing stack update, and the Security Monthly Quality Rollup. There may be some .NET Framework 4 updates as well. https://support.microsoft.com/en-us/help/4490628/...


2

SNMP is a protocol. Your legacy system is polling or receiving SNMP from what it's monitoring, and then storing that in SQL. The monitoring system is a program, it doesn't need an additional program to speak to SQL. It's probably got an ODBC or other connection to the database. Check the legacy system for existing ODBC connections. If it doesn't have any (...


1

This is most likely due to the wrong version of SSMS being installed. If you're absolutely sure you have the correct version of SQL server installed on your server, which you can test by opening services.msc and checking if the SQL Server Agent is present. then make sure you have the correct version of SSMS installed on your workstation. You can follow the ...


1

Found it - the solution is to give the service account access to create its own SPNs. To do that, simply grant SELF to read and write the servicePrincipalName field: Once you do that, you'll need to restart the SQL service. DO NOT USE THE SERVICES SNAP-IN WITH CLUSTERED SQL SERVERS! The Failover Cluster service will take this as a failure and cut it over.


1

http://msdn.microsoft.com/en-us/library/cc645993(v=sql.105).aspx#Scalability Espress won't use more than 1 GB of RAM for the SQL process. You need to buy and install at least Web or Standard to use more than 4 GB - they both support 64, which is more than you have, so go with one of those. Also, being a DBA is a pretty deep topic, but it's very accessible ...


1

Re-Installing the Basic-Management studio solved the problem.


1

Based on your requirements, there is no need for a new SQL Server instance As you don't need different SQL Server versions and your security and permissions requirements can be set on a single SQL Server instance, you can create a new database on the same instance Creating a new database on the existing SQL Server instance provides easier administration (...


Only top voted, non community-wiki answers of a minimum length are eligible