Xref: TK2MSFTNGP08.phx.gbl microsoft.public.sqlserver.server:339290 microsof
t.public.sqlserver.programming:440604
I am trying to dump out scripts for stored procedure and wondering how
I could exclude 'SET QUOTED_IDENTIFIER ON/OFF' option from the output.
I gather this option becomes part of stored procedure script on
creation time...!
I couldn't find any flags in SQL DMO that could be used to ignore this
option.
Please help...
Thanks
Sandiyanhi Sandiyan,
"sandiyan" <sandiyan@.yahoo.co.uk> ha scritto nel messaggio
news:69e9c64b.0404150614.632ccd9d@.posting.google.com...
> I am trying to dump out scripts for stored procedure and wondering how
> I could exclude 'SET QUOTED_IDENTIFIER ON/OFF' option from the output.
> I gather this option becomes part of stored procedure script on
> creation time...!
> I couldn't find any flags in SQL DMO that could be used to ignore this
> option.
> Please help...
i think the Object scripting constant
SQLDMO_SCRIPT_TYPE.SQLDMOScript_UseQuotedIdentifiers shoul'd be your case...
SQLDMOScript_UseQuotedIdentifiers , vaule= -1, description=Use quote
characters to delimit identifier parts when scripting object names
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||> i think the Object scripting constant
> SQLDMO_SCRIPT_TYPE.SQLDMOScript_UseQuotedIdentifiers shoul'd be your case.
.
> SQLDMOScript_UseQuotedIdentifiers , vaule= -1, description=Use quote
> characters to delimit identifier parts when scripting object names
Thanks. I tried this and it didn't work.
Help...
regards,
Sandiyan.sql
Showing posts with label public. Show all posts
Showing posts with label public. Show all posts
Wednesday, March 21, 2012
QUOTED_IDENTIFIER and SQL DMO
Xref: TK2MSFTNGP08.phx.gbl microsoft.public.sqlserver.server:339290 microsoft.public.sqlserver.programming:440604
I am trying to dump out scripts for stored procedure and wondering how
I could exclude 'SET QUOTED_IDENTIFIER ON/OFF' option from the output.
I gather this option becomes part of stored procedure script on
creation time...!
I couldn't find any flags in SQL DMO that could be used to ignore this
option.
Please help...
Thanks
Sandiyan
hi Sandiyan,
"sandiyan" <sandiyan@.yahoo.co.uk> ha scritto nel messaggio
news:69e9c64b.0404150614.632ccd9d@.posting.google.c om...
> I am trying to dump out scripts for stored procedure and wondering how
> I could exclude 'SET QUOTED_IDENTIFIER ON/OFF' option from the output.
> I gather this option becomes part of stored procedure script on
> creation time...!
> I couldn't find any flags in SQL DMO that could be used to ignore this
> option.
> Please help...
i think the Object scripting constant
SQLDMO_SCRIPT_TYPE.SQLDMOScript_UseQuotedIdentifie rs shoul'd be your case...
SQLDMOScript_UseQuotedIdentifiers , vaule= -1, description=Use quote
characters to delimit identifier parts when scripting object names
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||> i think the Object scripting constant
> SQLDMO_SCRIPT_TYPE.SQLDMOScript_UseQuotedIdentifie rs shoul'd be your case...
> SQLDMOScript_UseQuotedIdentifiers , vaule= -1, description=Use quote
> characters to delimit identifier parts when scripting object names
Thanks. I tried this and it didn't work.
Help...
regards,
Sandiyan.
I am trying to dump out scripts for stored procedure and wondering how
I could exclude 'SET QUOTED_IDENTIFIER ON/OFF' option from the output.
I gather this option becomes part of stored procedure script on
creation time...!
I couldn't find any flags in SQL DMO that could be used to ignore this
option.
Please help...
Thanks
Sandiyan
hi Sandiyan,
"sandiyan" <sandiyan@.yahoo.co.uk> ha scritto nel messaggio
news:69e9c64b.0404150614.632ccd9d@.posting.google.c om...
> I am trying to dump out scripts for stored procedure and wondering how
> I could exclude 'SET QUOTED_IDENTIFIER ON/OFF' option from the output.
> I gather this option becomes part of stored procedure script on
> creation time...!
> I couldn't find any flags in SQL DMO that could be used to ignore this
> option.
> Please help...
i think the Object scripting constant
SQLDMO_SCRIPT_TYPE.SQLDMOScript_UseQuotedIdentifie rs shoul'd be your case...
SQLDMOScript_UseQuotedIdentifiers , vaule= -1, description=Use quote
characters to delimit identifier parts when scripting object names
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||> i think the Object scripting constant
> SQLDMO_SCRIPT_TYPE.SQLDMOScript_UseQuotedIdentifie rs shoul'd be your case...
> SQLDMOScript_UseQuotedIdentifiers , vaule= -1, description=Use quote
> characters to delimit identifier parts when scripting object names
Thanks. I tried this and it didn't work.
Help...
regards,
Sandiyan.
Saturday, February 25, 2012
Quick and Easy question
I want to present an option to one of my clients to
switch from Exchange to an SQL database.
They are using Public folder for a lot and we get blamed
everytime something gets deleted by a user. They do have
a lot of data in PF. I also know that when something goes
awol and we have to restore the PF by dismounting PF and
taking everyone down for however long.
My questions are these:
How quickly can you restore SQL. Do you have to take the
whole database down to restore; can you restore just
certain tables, data, etc ..; can the users still work
away while restoring any portion of the database?
Thanks for all the help!!
Kevin
A database is unavailable while it is being restored (although it can be in
use while being backed-up). You can control the placement of individual
tables and indexes on filegroups and then backup or restore those filegroups
individually. You can also do a point-in-time restore which allows you to
roll back to a point before any data loss or corruption occurred.
However, you seem to be asking the wrong question. I don't know Exchange but
in SQLServer the solution to your problem is to implement user/object based
permissions so as to prevent users from deleting data that they are not
authorized to delete.
David Portas
SQL Server MVP
switch from Exchange to an SQL database.
They are using Public folder for a lot and we get blamed
everytime something gets deleted by a user. They do have
a lot of data in PF. I also know that when something goes
awol and we have to restore the PF by dismounting PF and
taking everyone down for however long.
My questions are these:
How quickly can you restore SQL. Do you have to take the
whole database down to restore; can you restore just
certain tables, data, etc ..; can the users still work
away while restoring any portion of the database?
Thanks for all the help!!
Kevin
A database is unavailable while it is being restored (although it can be in
use while being backed-up). You can control the placement of individual
tables and indexes on filegroups and then backup or restore those filegroups
individually. You can also do a point-in-time restore which allows you to
roll back to a point before any data loss or corruption occurred.
However, you seem to be asking the wrong question. I don't know Exchange but
in SQLServer the solution to your problem is to implement user/object based
permissions so as to prevent users from deleting data that they are not
authorized to delete.
David Portas
SQL Server MVP
Quick and Easy question
I want to present an option to one of my clients to
switch from Exchange to an SQL database.
They are using Public folder for a lot and we get blamed
everytime something gets deleted by a user. They do have
a lot of data in PF. I also know that when something goes
awol and we have to restore the PF by dismounting PF and
taking everyone down for however long.
My questions are these:
How quickly can you restore SQL. Do you have to take the
whole database down to restore; can you restore just
certain tables, data, etc ..; can the users still work
away while restoring any portion of the database?
Thanks for all the help!!
KevinA database is unavailable while it is being restored (although it can be in
use while being backed-up). You can control the placement of individual
tables and indexes on filegroups and then backup or restore those filegroups
individually. You can also do a point-in-time restore which allows you to
roll back to a point before any data loss or corruption occurred.
However, you seem to be asking the wrong question. I don't know Exchange but
in SQLServer the solution to your problem is to implement user/object based
permissions so as to prevent users from deleting data that they are not
authorized to delete.
--
David Portas
SQL Server MVP
--
switch from Exchange to an SQL database.
They are using Public folder for a lot and we get blamed
everytime something gets deleted by a user. They do have
a lot of data in PF. I also know that when something goes
awol and we have to restore the PF by dismounting PF and
taking everyone down for however long.
My questions are these:
How quickly can you restore SQL. Do you have to take the
whole database down to restore; can you restore just
certain tables, data, etc ..; can the users still work
away while restoring any portion of the database?
Thanks for all the help!!
KevinA database is unavailable while it is being restored (although it can be in
use while being backed-up). You can control the placement of individual
tables and indexes on filegroups and then backup or restore those filegroups
individually. You can also do a point-in-time restore which allows you to
roll back to a point before any data loss or corruption occurred.
However, you seem to be asking the wrong question. I don't know Exchange but
in SQLServer the solution to your problem is to implement user/object based
permissions so as to prevent users from deleting data that they are not
authorized to delete.
--
David Portas
SQL Server MVP
--
Quick and Easy question
I want to present an option to one of my clients to
switch from Exchange to an SQL database.
They are using Public folder for a lot and we get blamed
everytime something gets deleted by a user. They do have
a lot of data in PF. I also know that when something goes
awol and we have to restore the PF by dismounting PF and
taking everyone down for however long.
My questions are these:
How quickly can you restore SQL. Do you have to take the
whole database down to restore; can you restore just
certain tables, data, etc ..; can the users still work
away while restoring any portion of the database?
Thanks for all the help!!
KevinA database is unavailable while it is being restored (although it can be in
use while being backed-up). You can control the placement of individual
tables and indexes on filegroups and then backup or restore those filegroups
individually. You can also do a point-in-time restore which allows you to
roll back to a point before any data loss or corruption occurred.
However, you seem to be asking the wrong question. I don't know Exchange but
in SQLServer the solution to your problem is to implement user/object based
permissions so as to prevent users from deleting data that they are not
authorized to delete.
David Portas
SQL Server MVP
--
switch from Exchange to an SQL database.
They are using Public folder for a lot and we get blamed
everytime something gets deleted by a user. They do have
a lot of data in PF. I also know that when something goes
awol and we have to restore the PF by dismounting PF and
taking everyone down for however long.
My questions are these:
How quickly can you restore SQL. Do you have to take the
whole database down to restore; can you restore just
certain tables, data, etc ..; can the users still work
away while restoring any portion of the database?
Thanks for all the help!!
KevinA database is unavailable while it is being restored (although it can be in
use while being backed-up). You can control the placement of individual
tables and indexes on filegroups and then backup or restore those filegroups
individually. You can also do a point-in-time restore which allows you to
roll back to a point before any data loss or corruption occurred.
However, you seem to be asking the wrong question. I don't know Exchange but
in SQLServer the solution to your problem is to implement user/object based
permissions so as to prevent users from deleting data that they are not
authorized to delete.
David Portas
SQL Server MVP
--
Subscribe to:
Posts (Atom)