In my SQL Server database, I have a view which uses ssf.dse.ApplicationLog and ssf.dse.applications tables in the background.
The problem is - I can't find these tables in the database: they are not in the Tables folder, not in Views folder, or any other folder.
Did I miss something? What kind of tables have ssf.dse prefix?
ssf.dse.ApplicationLog means:
table ApplicationLog
in the dse schema
in the ssf database
So these tables are stored in a different database - that's why you're not seeing them in your own database ...
Related
I hope someone can help me to learn about Postgres schema and databases.
I have Postgres database called db1 and it has table calls table1.
all these objects are in default schema called public.
Then I created another database called db2 and created another table with same name table1.
I didn't got any error but both tables are in same schema called public.
I created indexes for both of these tables and they both refer the table as public.table1.
I wonder a setup like this will give issue or not? If yes, then should I create different schemas for each database if I'm going to use same table names in all databases?
In Postgres a database is the highest level "container". Then schemas follow. There can be schemas with the same name in different databases (but no in the same database). The other databases won't "see" them. So there is no problem in your setup.
Can we have two Postgres databases in same schema?
The answer is no. The relevant PostgreSQL documentation shows the hierarchy:
database.schema.table
This diagram (taken from this answer) is useful to visualise the relationship:
I have an Oracle linked server in SQL Server and would like to copy the contents of a number of views to a database in SQL Server, these views from Oracle are to become tables in SQL Server. I have done this one at a time but am looking for a solution to be able to refresh these views, 104 of them, overnight every night.
I am fine with setting the job running manually but am looking for a solution that will either drop and recreate the tables from the views or that will just refresh the data in the SQL Server tables that exist.
Hope I have explained this well enough!
Many thanks in advance for any help on this one.
If you don't already have the table structures in the MSSQL database, I'd say go through one time for all 104 views, and say the following:
SELECT *
INTO MSSQLNewTable (this will be the name of your new table)
FROM <However you reference your Oracle view from within MS SQL Server>
After you do that, then create a SQL Script that says:
TRUNCATE TABLE MSSQLTable_Name
INSERT INTO MSSQLTable_Name
SELECT * FROM OracleTable_Name
.....for each table. Create a job in the database instance that runs on a schedule you set.
use the sys. tables to generate the statements so you don't have to type everything 104 times.
I have a source database and a destination database with common tables. Is there any online tool that will sync the schema of tables in the source to destination ? Both databases are in MSSQL
Here are a couple of ideas:
Use Replication: http://www.howtoforge.com/mysql_database_replication
Use mysqldump in an import/export script to semi-automate it
If I have SQL tables tblA and tblB and they have one to many relationship between them.. can we create multiple raven db documents automatically .. Can I automatically load documents in Raven DB... from SQL server tables any other way... using any tool?
There is a ETL demo in Raven's code base.
Additionally, you may have a look at how Raccoon imports a SQL database for Subtext into RavenDB.
I have a database schema in SQL 2005 that I want to copy to a SQL 2000 server. It contains tables that have multiple owners. When I try to create a DTS package to transfer the schema I get conflicts because some of the tables have the same name (but different owners). It looks like it is trying to make all the tables to be owned by dbo.
Is there a way to preserve the ownership on the destination server?
It seems like there is no way to do this via DTS so I ended up scripting the database and recreating it from that script.