I newly installed SQL server 2012 .when install my Database their is a local server .then i created a db in local server about my new project.my system is in a network i install with admin permition. my db name is E4events and there are many tables in it.am also accessing network server db also from my sql server.i worked in local server db for 2 days on third day it is not connecting i refer and try to clear problem by many reference but still i cant connect .I am not feared about connection .i created lot of tables so if i can connect i will get data or otherwise please suggest me how to get that db and whole tables. so here below i attached meathods i tried to solve problem but i dint become succes
Related
I've set up 2 local SQL server databases, one on a laptop and the other on my desktop, I simply want to transfer the data my laptop gathers onto my desktop PC.
I've already managed to connect the 2 machines, from my desktop's SSMS I can see and query the laptop database.
Now I only need to transfer the data from the laptpop Server to my desktop, I tried with a simple
SELECT *
INTO [DesktopDB].[dbo].[TargetTable]
FROM [LaptopIP].[LaptopDB].[dbo].[SourceTable]
But I get this error:
OLE DB provider "MSOLEDBSQL" for linked server "LaptopIP" returned message "Cannot generate SSPI context".
Msg -2146893042, Level 16, State 1, Line 0
SQL Server Network Interfaces: No credentials are available in the security package
Can you please help me address this issue?
Thank you very much!
For Windows auth to work between servers without a domain, your username and password must be the same on both servers.
You can connect remote sql server as Linked server, than insert data into local database table from linked server
I have a problem on connecting microstrategy to a local database:
I'm unable to resolve this error, though I have tried everything in ODBC origins, and tried various drivers.
The server name is correct (SQLExpress2017)
If anyone knows how to resolve this issue, please help.
How to connect Micro Strategy 10 to SQL Server
We cannot connect the SQL SERVER 2017 through local by making the sql server dynamic access by allowing TCP/IP using(sql configuration manager)
NOTE
1)Within your network your system be accessible making dynamic sql server
After create odbc in Microstrategy server.in creating ODBC password should be your sql server username and password and create database instance in microstrategy.using datawarehouse catalog fetch the table based upon the instance you created
I am trying to connect to a database created in the SQL Server 2016 express edition, through Data Source Configuration Wizard in VS2017 Express edition, with SQL Server Authentication.
I created the user in SQL Server, and when I test the connection works perfectly, but vs displays the error. Also in Server properties, I set up SQL and Windows authentication.
I finally found a solution. I checked the checkbox remember password while creating connection string...and now can retrieve data for that user. In connection string is added persisted security=true. Still don't know why this need to be checked, because I follow example without persisted security, and there it worked, but on my PC didn't.
I am in the process of moving all our SharePoint DB's from a SQL 2005 server to a new 2008 server, and after moving the config database, everything seems ok, except when I click on "Timer Job Status" (under Central Admin > Operations > Global Configuration) I receive a "Unable to connect to database. Check database connection information and make sure the database server is running." error.
I get the following entries in the log regarding this:
12/03/2010
13:51:41.80
w3wp.exe
(0x09E0)
0x09AC
Windows SharePoint Services
General
8e2r
Medium
Possible mismatch
between the reported error with code =
0x8107053b and message: "Unable to
connect to database. Check database
connection information and make sure
the database server is running." and
the returned error with code
0x81020024.
12/03/2010
13:51:45.61
OWSTIMER.EXE
(0x0744)
0x0DD8
Windows SharePoint Services
Database
6f8e
Critical
SQL Database
'SP_Test_Config' on SQL Server
instance 'test-server' not found.
Additional error information from SQL
Server is included below. Cannot open
database "SP_Test_Config" requested by
the login. The login failed.
It should be noted that in order to ensure that it was no longer using the config database on the old server, I detached the original SP_Test_Config database in SQL Management Studio.
Obviously there are still references to the old SP_Test_Config database on the old 2005 server. How do I remove these references? Or, barring that, how do I move the config database in such a way that no references to the old 2005 server will remain?
Thank you in advance!
Not really an answer, but what we ended up doing (basically start from scratch using SQL Aliases):
First, create the SQL Server alias. This will make it so if you need to move the databases again in the future, you can just migrate all the databases to the new SQL Server, and change your SQL Server alias to point at that server. This should save you a lot of trouble and heartache in the future.
Run SQL Server Client Configuration Utility at: C:\Windows\System 32\cliconfig.exe.
Under the Alias tab, create a SQL Server Alias for the new SQL Server.
Now, recreate the farm.
Run stsadm -o preparetomove on all content DB's Backup all content DB's and copy to new SQL server
Remove all servers from farm using SharePoint Configuration Wizard
Recreate farm using SharePoint Configuration Wizard with the alias of the SQL Server you created above
Recreate all web apps with temp content DB's
Run stsadm -o deletecontentdb on all temp content databases created in step 4
Run stsadm -o addcontentdb using copied production databases as content database
Troubleshoot ad nauseum
I am migrating a classic ASP web app to new servers. The database back end is migrating from SQL Server 2000 to SQL Server 2008, and the app is moving from Win2000 x86 to Win2003R2 x64. I am getting the above error on every single stored procedure call within the application.
I have verified:
Yes, the SQL user is set up, using correct username and password
Yes, the SQL user has execute permissions on the stored procedures in the database
Yes, I have updated the TypeLib references to the new UUID
Yes, I have logged into the database via SSMS with the SQL user id and it can see and execute the stored procedures just fine in SSMS, but not from the web app.
Yes, the SQL user has the database set as its default database.
The most frustrating thing is it works fine on the DEV server, but not on the production server. I have gone through every IIS setting 5 or 6 times and the web app is set up precisely the same in both environments. The only difference is the database server name in the connection string (DEV vs prod)
EDIT: I have also tried pointing the prod web box at the dev database server and get the same error so I'm fairly sure the issue isn't on the database side.
Are you sure that you are really connected to the instance and database you think you are (in the App)? It only takes the wrong DB in the connection string to override the default database for the user.
Can you execute some inline SQL on the connection like:
SELECT ##SERVERNAME AS SERVERNAME
,DB_NAME() AS [DB_NAME]
,CURRENT_USER AS [CURRENT_USER]
It might be the schema. Have you set the default schema of your user in the database you are using?