I have a user who has been granted db_owner rights to a database and want him to be able create new views using the dbo schema. When the user creates a view right now, the schema created is under their username. How can I change this so that when a user creates a new view, they always create it under the dbo schema.
A co-worker recently quit the company, and all of his storedprocedures and DTS packages are apparently under his name. Is thereany way to change his account to another (ie administrator or SA)??I am afraid to delete his account in fear all the stored procedureswill be lost. (we have backups, but ... ugh)
I have a problem while executing a stored procedure. I have created a database called "cpd" and created some stored procedures. for all my stored procedure the owner is "CPDUSER". when ever i am executing any stored procedures i have to write the user name first else it is not working.
let's say i have a stored procedure called "cp_checklogin". it takes 2 parameters. to execute this i have to write
but i don't want to write the user name there. and if without username "CPDUSER" i am trying to execute the stored procedure it is throwing me the error that "the stored procedure cp_checklogin is not exist in the database". can anybody suggest me. it's very urgent.
Here's one. :) I have Database A in Server 1 which contains objects (tables and SPs) that are owned by users other than dbo. Then I detach this database from Server 1 using sp_detach_db and attach it to Server2 (sp_attach_db). Even if the same logins exist or are created in Server 2, I still won't be able to access the objects in Database A using these logins. I know that this happens because of different SIDs for the same login names across the 2 servers. So given that I want to achieve this without having to use the Import Wizard or any other method, how do I go around this lil bit of a problem? Any thoughts? :)
we have a group of developers which have created and asked us (DBAs) tocreate many objects in the databases including tables / storedprocedures / functions / etc.since our company is growing, however we have an increasing amount ofobjects that have either been abandoned or have several versions.in an effort to clean of the huge amount of clutter and anytime thatsomething simple like a stored proc needs to change, it is almostimpossible to predict exactly where we will see negative effects ofthis change.i am looking for a system (preferably without developing our own tool)that would keep track of history of database objects (in terms of whocreated it and what purpose it has) as well as link that to all thedevelopers/users we might need to notify of any changes to that object.Also, this should be linked to the application which rely on theobject.bottom line... every object in the database needs to have at least 1corresponding contact as well as the applications which us it.with this information, we can much more easily maintain objects in ourDBs.thx
Logged in under a login id that is a db_owner on a database, I can not bind a rule owned by dbo to a table owned by dbo. Following does not work: EXEC sp_bindrule 'dbo.rule1', 'table1.column1' error:You do not own a table named 'table1' that has a column named 'column1'.
Following does not work: EXEC sp_bindrule 'dbo.rule1', 'dbo.table1.column1' error: Rule,table and user datatype must be in current database
To bind the rule, I had to change table ownership to my login id and then bind the rule. I then changed table ownership back to dbo. This method seems odd. I do not have this problem when binding defaults to dbo owned tables.
Just installed VS 2005 & SQLServer 2005 clients on my workstation. When trying to create a new Integration Services Project and start work in the designer receive the MICROSOFT VISUAL STUDIO 'Object reference not set to an instance of an object.' dialog box with message "Creating project 'Integration Services project1'...project creation failed."
Previously I had SQLServer 2000 client with the little VS tool that came with it installed. Uninstalled these prior to installing the 2005 tools (VS and SQLServer).
I'm not finding any information on corrective action for this error.
I have read many threads on this issue & tried multiple solutions to no avail.
Here's my environment: SQL 2000, Logged directly into server via VPN (so it should be like I am physically at the server).
I've set up a DTS Package that executes an Access procedure. The package runs fine when I execute manually. When I execute via schedule, it fails on the error "ActiveX component can't create object: 'Access.Application'. The actual statement is:
Set objDB = CreateObject("Access.Application")
I know that Scheduled jobs default back to the SQL Agent permissions. I have reset SQL Agent to use my Windows NT account login so it should have the exact same permissions, etc. that I have when I execute manually?
I am new to sql server. right now i getting used to management studio.I am trying to creata a new object / a new database but i am getting an error which says permission not granted
Here's one thing that I'd like to see come out in some version of the SQL Server Management Studio... The ability to create folders under the database node so that databases can be grouped on one server.
We have over 100 databases on our development server and these are created by a range of consultants and developers and even support staff as needed.
Being able to group the databases by product, etc would be a nice touch since we have client databases that don't fit naming conventions etc.
Multiple instances are another way around this but are expensive and resource hungry - we develop and support models, not use them for transactions too much.
Yes there are 'better' ways such as setting security correctly but we are too busy working and not maintaining.
User bob has create procedure permission as follows:
grant create procedure to bob
bob would like to create a procedure in schema Accounts.
When he issues create proc Accounts.sp_proc.... it fails with:
Msg 2760, Level 16, State 1, Procedure sp_proc, Line 3 The specified schema name "Accounts" either does not exist or you do not have permission to use it.
What permission do I need to grant bob in order to allow this?
I've created a DTS package which exec's perfectly throught the DTS interface, but when I try to run the same package in a Job using DTSRun, I'm getting the following error... #### DTSRun: Loading... DTSRun: Executing... DTSRun OnStart: DTSStep_DTSActiveScriptTask_1 DTSRun OnError: DTSStep_DTSActiveScriptTask_1, Error = -2147220482 (800403FE) Error string: Error Code: 0 Error Source= Microsoft VBScript runtime error Error Description: ActiveX component can't create object: 'CreateObject' Error on Line 15 Error source: Microsoft Data Transformation Services (DTS) Package Help file: sqldts.hlp Help context: 1100
Error Detail Records: Error: -2147220482 (800403FE); Provider Error: 0 (0) Error string: Error Code: 0 Error Source= Microsoft VBScript runtime error Error Description: ActiveX component can't create object: 'CreateObject' Error on Line 15 Error source: Microsoft Data Transformation Services (DTS) Package Help file: sqldts.hlp Help context: 1100 DTSRun OnFinish: DTSStep_DTSActiveScriptTask_1 DTSRun: Package execution complete.
####
The 1st part of the actual ActiveX script within the DTS package is...
If I create an Active Script like this : function Main() Dim fso Dim a Set fso = CreateObject("Scripting.FileSystemObject") Set a = fso.CreateTextFile("c:est.txt") a.WriteLine("This is a test") a.Close end Function
I got an error ErrorCOde: 0 ErrorSource : VBScriptENgineError Error Description : ActiveX Component can't create object : CreateObject
Hello,I am attempting to send emails using T-SQL (in a SQLServerAgent Job)using the stored procedure sp_SendSMTPMail. I created the stored procusing the following script that I got off a post here on google.CREATE PROCEDURE sp_SendSMTPMail (@From varchar(255),@To varchar(8000),@Subject varchar(255),@Body varchar(8000),@cc varchar(8000) = NULL,@Bcc varchar(8000) = NULL)ASDECLARE @newmail intDECLARE @result int-- Create the CDONTS.Newmail objectEXEC @result = sp_OACreate 'CDONTS.NewMail', @newmail OUTIF @result <> 0BEGINPRINT 'Error creating object'EXEC sp_displayoaerrorinfo @newmail, @resultRETURNEND-- Check the Optional PropertiesIF not @cc = NULLBEGINEXEC @result = sp_OASetProperty @newmail, 'cc', @ccIF @result <> 0BEGINPRINT 'Error setting [cc] property'-- EXEC sp_displayoaerrorinfo @newmail, @resultRETURNENDENDIF not @Bcc = NULLBEGINEXEC @result = sp_OASetProperty @newmail, 'Bcc', @BccIF @result <> 0BEGINPRINT 'Error setting [Bcc] property'-- EXEC sp_displayoaerrorinfo @newmail, @resultRETURNENDEND--set the non-optional propertiesEXEC @result = sp_OASetProperty @newmail, 'From', @FromEXEC @result = sp_OASetProperty @newmail, 'To', @ToEXEC @result = sp_OASetProperty @newmail, 'Subject', @SubjectEXEC @result = sp_OASetProperty @newmail, 'Body', @Body-- Send the message...EXEC @result = sp_OAMethod @newmail, 'Send'IF @result <> 0BEGINPRINT 'Error sending message'-- EXEC sp_displayoaerrorinfo @newmail, @resultRETURNEND-- Destroy the object.EXEC @result = sp_OADestroy @newmailIF @result <> 0BEGINPRINT'Error destroying object'-- EXEC sp_displayoaerrorinfo @newmail, @resultRETURNENDGO______________________________________________This worked perfectly in testing at our office but when we shipped tothe client it produced the error 'Error creating object'. We sent theclient the script to create the sp_displayoaerrorinfo proc and got thefollowing error message.Error creating object-2147221005OLE Automation Error InformationHRESULT: 0x800401f3Source: ODSOLE Extended ProcedureDescription: Invalid class stringNow this suggested to me that the for some reason we were unable toreference the CDO library, or it wasn't installed. However they haveOutlook 2000 installed with CDO installed with it. I've had had themremove and reinstall the CDO library but that hasn't helped.Other thing I though of was a permission type problem. They are usingNT authentication for there logins into SQL server and are logged onthe server as Administrator who I would assume has all requiredpermissions.Any suggestions for either determining the cause of them problems or asolution?Thanks in advance.Bob.
I'm developing a report in SQL Server 2005 Reporting Services based on a query from SQL Server tables joined with Visual FoxPro free tables. I created a Linked Server with Microsoft OLE DB Provider for Visual FoxPro provider, whith VFPOLEDB.1 string provider. Everything runs ok within a Business Intelligence Development Studio environment, but when I implement my report, at runtime an error occurs it said "Cannot create an instance of OLE DB Provider VFPOLEDB object". I swtched any combination of Linked Server security and Provider security pages without to solve the problem.
Navigating the web today, I read a similar thread posted by stephanielauym at April 3, 2006 but I`m not clear if she passed the issue or not. In case of yes, I would like to know how she solved it. I'proved among other with "Allow inprocess" but don't.
Please, if Stephany or Cindy (that she answered) or anyone knows how to solve this error, I'll thank very much.
Arturo Carrión artcarrion@yahoo.com.ar at Tiempo Hard SA Mendoza, Argentina
I have a new instance (SQL 2012) and I am trying to create a cube but it retrieves the error: Either the 'NameUser' user does not have permission to create a new object in 'NameServer' or the object does not exist. I am not the DBA but I got privilege as administrator in my instance. I even checked the propierties (right click on the analysis service instance) and in security there is my name as well..
I'm using SQL Server 2008R2. I am developing a database which requires access to data from other servers. So far I have been creating views using OPENQUERY (where there's a performance benefit) to select specifically the columns I want. Generally, for my purposes, I find these OPENQUERY based views to perform better (some times significantly so) to simple SELECT <COLUMNS> FROM <SERVER>.<DATABASE>.<SCHEMA>.<TABLE> WHERE <Where clause Statements> format views. My understanding is that this is because an OPENQUERY "pushes" the query processing to the remote server and simply returns the final result set to the local server i.e. there's no cross-server join/synchronization going on.
My question is, if I were to create a Synonym for a table object on the remote server, where does the processing happen if I query from this Synonym or create a join with this synonym to a table in my local database?Essentially, I am trying to understand if there are any "hidden gotcha's" primarily from a performance perspective, to using synonyms.
I have the same database(3GB) in 2 physical locations in usa and europe
I need to create a publisher and subscriber between these 2 database without sending any snapshot because i have the same data in the 2 sides, is it possible ?
We are in the process of trying to automate our production releases (what a concept ;-)
The database is SQL server 2005 All objects are being stored in VSS Using Nant and Cruise Control for the actual migrations. I have two directories - Create (for a brandnew database) and Change (db object changes)
In my 'Change' script, I do the following -
1 - Take backup of database 2 - Migrate objects from 'change' directory to production 3 - Script out all objects of database and save in the 'Create' directory
For the #3, I was hoping I could create an SSIS package that would script out all database objects and save them on the VSS server.
I'm new to SSIS and want to verify it's something that can be done before I start down that path. If anyone has any examples or references, it would be much appreciated.
We've all seen this, where it uses an individual .write statement for each column.
Code Snippet
Public Overrides Sub AWCCogent_ProcessInputRow(ByVal Row As AWCCogentBuffer)
With textWriter
Dim item As Object
If Not Row.AddressID_IsNull Then .Write(Row.AddressID) End If .Write(columnDelimiter) If Not Row.City_IsNull Then .Write(Row.City) End If
.WriteLine()
End With
End Sub
But hard coding this seems not the smartest way. Especially since in my text file, there needs to be close to 100 columns. This could be a nightmare to update down the road. But I can't seem to find the object collection to loop through, like row.items which would seem to be logical.
We have installed 2014 sql server on a stand alone VM and can create alerts without issue. We recently did a cluster install of 2014, and when trying to create alerts get the following error:
Msg 14262, Level 16, State 1, Procedure sp_verify_performance_condition, Line 52 The specified object_name ('Databases') does not exist.
Specifically, we are trying to create a database alert on percent log used that will kick off a job to back up the log.
We are on Windows 2012R2 o/s. In the drop downs in SSMS under alerts, we do not have all the options we have in the stand alone instance - they are not there. Is this a bug? Is there a CU?
I am using the Import/Export wizard to import data from an ODBC data source. This can only be done from a query to specify the data to transfer.
When I try to create the tables, for the query, I am getting the following error:
Msg 2714, Level 16, State 4, Line 12
There is already an object named 'UserID' in the database.
Msg 1750, Level 16, State 0, Line 12
Could not create constraint. See previous errors.
I have duplicated this error with the following script:
USE [testing]
IF OBJECT_ID ('[testing].[dbo].[users1]', 'U') IS NOT NULL
DROP TABLE [testing].[dbo].[users1]
CREATE TABLE [testing].[dbo].[users1] (
[UserID] bigint NOT NULL,
[Name] nvarchar(25) NULL,
CONSTRAINT [UserID] PRIMARY KEY (UserID)
)
IF OBJECT_ID ('[testing].[dbo].[users2]', 'U') IS NOT NULL
DROP TABLE [testing].[dbo].[users2]
CREATE TABLE [testing].[dbo].[users2] (
[UserID] bigint NOT NULL,
[Name] nvarchar(25) NULL,
CONSTRAINT [UserID] PRIMARY KEY (UserID)
)
IF OBJECT_ID ('[testing].[dbo].[users3]', 'U') IS NOT NULL
DROP TABLE [testing].[dbo].[users3]
CREATE TABLE [testing].[dbo].[users3] (
[UserID] bigint NOT NULL,
[Name] nvarchar(25) NULL,
CONSTRAINT [UserID] PRIMARY KEY (UserID)
)
I have searched the "2714 duplicate error msg," but have found references to duplicate table names, rather than multiple field names or column name duplicate errors, within a database.
I think that the schema is only allowing a single UserID primary key.
Sometime ago, I had read a posting here about where in the system we can specify default owner of all objects in user database as being a DBO.
The topic came about, because somebody found out that if an object referred to in a query, does not have a fully qualified name, then it takes some time for SQL server to figure out what the owner of the object is; this causes performance problems. e.g. select * from employees and select * from dbo.employees.
If anybody knows what that setting is...I will really appreciate it
My system was crashing so I reinstalled everything. including SQL 2005 Express with management studio. I renamed the computer from the previous install. but for some reason the sql 2005 express management studio remembers the old machine name even when I create a new DB inside the management studio with the new computer name.when I try to change the ownership in properties-files it cant find the 'new computer nameuser'i double checked the computer name its correct. The funny thing is i installed express with the 'new computerame' anyone have a clue that may help with this what file needs to be edited?Thanks inadvance for any help.
Is there a way in SS 7.0 to change ownership of an object from a user owned object to dbo owned object other than dropping the object and re-creating it? E.G. juser.table to dbo.table Thank you, GaetonC
Is there anyway to change the ownership of a table.. I have developers who create tables and the tables are then shown to be owned by them.. These developers are in the db_owner database role.. The application will not run successfully unless the table is owned by the dbo..
The only way I see that I can handle this is to have them generate a script and have myself (full sa) run it..
I work in a development team of 5 people - when we create DTS packages they are owned by the individuals' user. This means that if a problem is discovered, only the original developer can change their package - which is a problem if they are busy / on holiday etc.
Is there a way to change each others packages without having System Admin priveleges (definitely not an option)
Similarly, how are people handling version control of packages - they is no way to put a package into Sourcesafe / something similar is there ?
I am having a problem with object ownership. The person who setup the SQL Server setup the "dbo" account with his personal permissions. I need to change "dbo" so that the login name is the system account and not a personal account. Is this possible?
If this is not possible can I change the ownership of a system object? I was able to change ownershipof user objects using the "sp_changeobjectowner" stored procedure, but it did not seem to work for system objects.
One of my apps uses a login that is tied down to only use the sprocs and tables it is allowed to access. Its just given 'public' role. However, it needs to be able to add and delete fields from one table in particular. Is there a way to allow this? The login it uses has been given full rights to the table but an alter table command faults. The tbale must be a 'dbo' because other apps use it -- can I be granted DDL rights on a per table basis?